Skip to content
CI

Rename from Alfalfa to PACER Webservice #1462

Sign in to view logs

Rename from Alfalfa to PACER Webservice

Rename from Alfalfa to PACER Webservice #1462

Triggered via push March 13, 2026 19:46
@TShapinskyTShapinsky
pushed 0ced796
pacer_rename
Status Failure
Total duration 19m 32s
Artifacts 3

ci.yml

on: push
Pre-commit checks
37s
Pre-commit checks
Run unit tests
1m 34s
Run unit tests
Run simulation tests in worker
2m 33s
Run simulation tests in worker
Run integration tests
18m 5s
Run integration tests
Run integration tests with historian
19m 27s
Run integration tests with historian
Build and publish Docker images
0s
Build and publish Docker images
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 6 warnings
Pre-commit checks
Process completed with exit code 1.
Run simulation tests in worker
Process completed with exit code 1.
Pre-commit checks
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/checkout@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/
Run unit tests
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@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/
Run simulation tests in worker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/bake-action@v5, docker/setup-buildx-action@v3, jwalton/gh-docker-logs@v2. 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/
Run integration tests
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@v5, docker/bake-action@v5, docker/setup-buildx-action@v3, jwalton/gh-docker-logs@v2. 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/
Run integration tests with historian
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@v5, docker/bake-action@v5, docker/setup-buildx-action@v3, jwalton/gh-docker-logs@v2. 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/
Sensitive data should not be used in the ARG or ENV commands: grafana/Dockerfile#L7
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "INFLUXDB_ADMIN_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size Digest
NatLabRockies~alfalfa~1UW3AO+2.dockerbuild Expired
187 KB
sha256:3f45bf9f5d4c043fd7134b4f4fa40e528b497f22a5fa90a7a783a6f665b6b0e0
NatLabRockies~alfalfa~GTR00W+1.dockerbuild Expired
110 KB
sha256:536510cfd25d53ca4f1950ece2d49027354b58b190c4b1c1d279e2be957d1879
NatLabRockies~alfalfa~KD50VV+1.dockerbuild Expired
116 KB
sha256:ad5eee5681e40ab08e5d6f2013a1e1e08df2044b449d838bff971f91efa1babf