Skip to content

Infra Update v8: spack v1 Support #200

Infra Update v8: spack v1 Support

Infra Update v8: spack v1 Support #200

Triggered via pull request March 20, 2026 01:23
Status Failure
Total duration 1h 3m 9s
Artifacts 1

ci.yml

on: pull_request
Matrix: CI / Deploy
CI  /  !redeploy Pending
0s
CI / !redeploy Pending
Matrix: Closed / undeploy-prereleases
Waiting for pending jobs
CI  /  Post-Deploy Notifier
17s
CI / Post-Deploy Notifier
CI  /  !redeploy Status ${{ needs.deploy.result }}
0s
CI / !redeploy Status ${{ needs.deploy.result }}
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 6 warnings, and 1 notice
CI / Deploy (Gadi) / Gadi: Check Spack Manifest
Process completed with exit code 1.
CI / Deploy (Gadi) / Gadi / Deploy to Gadi Prerelease
Process completed with exit code 3.
CI / Setup CI
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/
CI / Deploy (Gadi) / Gadi: Check Spack Manifest
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/
CI / Deploy (Gadi) / Gadi: Check Config
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, GrantBirki/json-yaml-validate@d7814b94473939c1daaca2c96131b891d4703a3c. 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/
CI / Deploy (Gadi) / Gadi / Deploy to Gadi Prerelease
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/setup-python@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/
CI / Deploy (Gadi) / Gadi:Outputs Upload
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
CI / Post-Deploy Notifier
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/download-artifact@v4, actions/setup-python@v5. 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/
CI / Deploy (Gadi) / Gadi: Check Spack Manifest
DEBUG: The previous version of the manifest will only be available via the old get-root-spec-ref action. This will not be the case for the actual update

Artifacts

Produced during runtime
Name Size Digest
deploy-access-am3-outputs.Gadi
620 Bytes
sha256:6dc38e88949370bc656e8c11531eca3b7f9bc58fa12f12de2b2aac5e9d4209ea