Remove . tests and 6.4.0 tests
#9
ArchangelX360ci.yaml
on: push
pre-commit
13s
test
/
matrix-prep-os
4s
test
/
matrix-prep-bazelversion
5s
Matrix: test / test
conclusion
3s
Annotations
5 errors and 21 warnings
|
pre-commit
Process completed with exit code 1.
|
|
test / test (ubuntu-latest, 6.4.0, e2e/smoke, true)
Process completed with exit code 37.
|
|
test / test (macos-latest, 6.4.0, e2e/smoke, true)
Process completed with exit code 37.
|
|
test / test (windows-latest, 6.4.0, e2e/smoke, true)
Process completed with exit code 1.
|
|
conclusion
Process completed with exit code 1.
|
|
test / matrix-prep-bazelversion
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 2nd, 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/
|
|
pre-commit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test / test (ubuntu-latest, 6.4.0, e2e/smoke, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, andstor/file-existence-action@v3, p0deje/setup-bazel@0.6.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test / test (ubuntu-latest, 6.4.0, e2e/smoke, true)
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
at Object.<anonymous> (/home/runner/work/_actions/p0deje/setup-bazel/0.6.0/dist/webpack:/setup-bazel/node_modules/@actions/cache/lib/cache.js:175:1)
at Generator.next (<anonymous>)
at fulfilled (/home/runner/work/_actions/p0deje/setup-bazel/0.6.0/dist/webpack:/setup-bazel/node_modules/@actions/cache/lib/cache.js:28:1)
|
|
test / test (ubuntu-latest, 6.4.0, e2e/smoke, true)
Failed to restore: Cache service responded with 400
|
|
test / test (macos-latest, 6.4.0, e2e/smoke, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, andstor/file-existence-action@v3, p0deje/setup-bazel@0.6.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test / test (macos-latest, 6.4.0, e2e/smoke, true)
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
at Object.<anonymous> (/Users/runner/work/_actions/p0deje/setup-bazel/0.6.0/dist/webpack:/setup-bazel/node_modules/@actions/cache/lib/cache.js:175:1)
at Generator.next (<anonymous>)
at fulfilled (/Users/runner/work/_actions/p0deje/setup-bazel/0.6.0/dist/webpack:/setup-bazel/node_modules/@actions/cache/lib/cache.js:28:1)
|
|
test / test (macos-latest, 6.4.0, e2e/smoke, true)
Failed to restore: Cache service responded with 400
|
|
test / test (macos-latest, 9.0.0, e2e/smoke, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, andstor/file-existence-action@v3, p0deje/setup-bazel@0.6.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test / test (macos-latest, 9.0.0, e2e/smoke, true)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0X0/EaQAAAAA6oMt8teqSQ74b4BrzGjV7UEFPRURHRTA2MTUARWRnZQ==
|
|
test / test (macos-latest, 9.0.0, e2e/smoke, true)
Failed to restore: Cache service responded with 400
|
|
test / test (windows-latest, 6.4.0, e2e/smoke, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, andstor/file-existence-action@v3, p0deje/setup-bazel@0.6.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test / test (windows-latest, 6.4.0, e2e/smoke, true)
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
at Object.<anonymous> (D:\a\_actions\p0deje\setup-bazel\0.6.0\dist\webpack:\setup-bazel\node_modules\@actions\cache\lib\cache.js:175:1)
at Generator.next (<anonymous>)
at fulfilled (D:\a\_actions\p0deje\setup-bazel\0.6.0\dist\webpack:\setup-bazel\node_modules\@actions\cache\lib\cache.js:28:1)
|
|
test / test (windows-latest, 6.4.0, e2e/smoke, true)
Failed to restore: Cache service responded with 400
|
|
test / test (ubuntu-latest, 9.0.0, e2e/smoke, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, andstor/file-existence-action@v3, p0deje/setup-bazel@0.6.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test / test (ubuntu-latest, 9.0.0, e2e/smoke, true)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0e0/EaQAAAACT8v/v0N0eSbbiJb+Uh5QpUEFPRURHRTA1MTAARWRnZQ==
|
|
test / test (ubuntu-latest, 9.0.0, e2e/smoke, true)
Failed to restore: Cache service responded with 400
|
|
test / test (windows-latest, 9.0.0, e2e/smoke, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, andstor/file-existence-action@v3, p0deje/setup-bazel@0.6.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test / test (windows-latest, 9.0.0, e2e/smoke, true)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0gk/EaQAAAACkAzaSYMeLQqvPzH4kcWeCUEhMMzBFREdFMDIxNQBFZGdl
|
|
test / test (windows-latest, 9.0.0, e2e/smoke, true)
Failed to restore: Cache service responded with 400
|
|
conclusion
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: technote-space/workflow-conclusion-action@45ce8e0eb155657ab8ccf346ade734257fd196a5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|