Skip to content

CI (feat_rbac_is_back) #7191

CI (feat_rbac_is_back)

CI (feat_rbac_is_back) #7191

Triggered via pull request June 8, 2026 19:20
Status Failure
Total duration 43m 3s
Artifacts

main.yml

on: pull_request
Matrix: main / test / hsm
Matrix: main / test / test-nix
main  /  ...  /  windows - cargo test
24m 47s
main / test / windows-2022 / windows - cargo test
main  /  ...  /  windows - UI E2E tests
26m 8s
main / test / windows-2022 / windows - UI E2E tests
main  /  ...  /  windows - CNG KSP integration tests
22m 21s
main / test / windows-2022 / windows - CNG KSP integration tests
main  /  ...  /  clippy
6m 45s
main / cargo-clippy / clippy
main  /  ...  /  audit
5m 52s
main / Security Audit / audit
main  /  ...  /  machete
1m 19s
main / cargo-machete / machete
main  /  ...  /  forward-proxy
9m 3s
main / forward-proxy / forward-proxy
main  /  public_documentation
26s
main / public_documentation
main  /  ...  /  cla-assistant
main / cla-assistant / cla-assistant
Matrix: main / cargo-test
main  /  ...  /  cache_cleanup
main / test / cleanup / cache_cleanup
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 4 warnings
main / Security Audit / audit
Process completed with exit code 1.
main / cargo-clippy / clippy
Process completed with exit code 101.
main / No Nix - ubuntu-24.04-arm - sqlite - non-fips
Process completed with exit code 101.
main / No Nix - ubuntu-24.04 - sqlite - non-fips
Process completed with exit code 101.
main / No Nix - macos-15 - sqlite - non-fips
Process completed with exit code 101.
main / test / Test on sqlite - non-fips
Process completed with exit code 101.
main / test / Test on psql - non-fips
Process completed with exit code 101.
main / test / Test on percona - non-fips
Process completed with exit code 101.
main / test / Test on redis - non-fips
Process completed with exit code 101.
main / test / Test on mysql - non-fips
Process completed with exit code 101.
main / test / windows-2022 / windows - cargo test
Process completed with exit code 1.
main / test / Test on mariadb - non-fips
Process completed with exit code 101.
main / cargo-machete / machete
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
main / Security Audit / audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-rs/audit-check@v1, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
main / Security Audit / audit
1 warnings found!
main / cargo-clippy / clippy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/