Skip to content
CI

Fix container name in ci #1464

Sign in to view logs

Fix container name in ci

Fix container name in ci #1464

Triggered via push March 13, 2026 20:29
@TShapinskyTShapinsky
pushed edd49e8
pacer_rename
Status Cancelled
Total duration 12m 6s
Artifacts 2

ci.yml

on: push
Pre-commit checks
20s
Pre-commit checks
Run unit tests
1m 37s
Run unit tests
Run simulation tests in worker
18s
Run simulation tests in worker
Run integration tests
12m 2s
Run integration tests
Run integration tests with historian
11m 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

7 errors and 6 warnings
Pre-commit checks
Process completed with exit code 1.
Run simulation tests in worker
cannot parse bake definitions: ERROR: open docker-compose.yml: no such file or directory
Run integration tests
The run was canceled by @TShapinsky.
Run integration tests
The operation was canceled.
Run integration tests with historian
The run was canceled by @TShapinsky.
Run integration tests with historian
The operation was canceled.
CI
The run was canceled by @TShapinsky.
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 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 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 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~1JZCI9+1.dockerbuild Expired
110 KB
sha256:3f42a885caeee5e243f067c63bbbebe1060e06d81b121e16b412d7446b949698
NatLabRockies~alfalfa~1M5192+2.dockerbuild Expired
182 KB
sha256:c560f4a394a4132d879e9e1171c698e91903a6241a66b8c9ebdfeb905b8c7bfe