Skip to content

Bump alpine from 3.20 to 3.23 in /infrastructure #22

Bump alpine from 3.20 to 3.23 in /infrastructure

Bump alpine from 3.20 to 3.23 in /infrastructure #22

Triggered via pull request April 3, 2026 10:32
Status Failure
Total duration 3m 12s
Artifacts

ci-optimized.yml

on: pull_request
Detect Changes
7s
Detect Changes
Matrix: unit-tests
Integration Tests
49s
Integration Tests
Lint Frontend
0s
Lint Frontend
Lint Go
0s
Lint Go
Frontend Tests
0s
Frontend Tests
Tests gate
4s
Tests gate
Matrix: build-images
Performance Tests (k6)
0s
Performance Tests (k6)
Deploy (disabled)
0s
Deploy (disabled)
CI Report
3s
CI Report
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 8 warnings
Security Scan
controller.newOTLPTracerProvider calls trace.WithBatcher, which eventually calls env.BatchSpanProcessorScheduleDelay
Security Scan
controller.newOTLPTracerProvider calls trace.WithBatcher, which eventually calls env.BatchSpanProcessorMaxQueueSize
Security Scan
controller.newOTLPTracerProvider calls trace.WithBatcher, which eventually calls env.BatchSpanProcessorMaxExportBatchSize
Security Scan
controller.newOTLPTracerProvider calls trace.WithBatcher, which eventually calls env.BatchSpanProcessorExportTimeout
Security Scan
controller.HealthChecker.checkAgents calls http.Client.Do, which eventually calls url.URL.Parse
Security Scan
controller.main calls http.ListenAndServe, which eventually calls url.ParseRequestURI
Security Scan
controller.newOTLPTracerProvider calls url.Parse
Security Scan
controller.main calls trace.TracerProvider.Shutdown, which eventually calls os.ReadDir
Security Scan
controller.main calls http.ListenAndServe, which eventually calls template.Template.ExecuteTemplate
Security Scan
controller.main calls http.ListenAndServe, which eventually calls template.Template.Execute
Security Scan
Process completed with exit code 1.
Build dashboard image
buildx failed with: ERROR: failed to build: invalid tag "ghcr.io/fraware/chaoslabs/dashboard:-19656b6": invalid reference format
Build controller image
buildx failed with: ERROR: failed to build: invalid tag "ghcr.io/fraware/chaoslabs/controller:-19656b6": invalid reference format
Build agent image
buildx failed with: ERROR: failed to build: invalid tag "ghcr.io/fraware/chaoslabs/agent:-19656b6": invalid reference format
CI Report
Unable to resolve action thollander/comment-pull-request, repository not found
Detect Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
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-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Security Scan
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-go@v5, github/codeql-action/upload-sarif@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Security Scan
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
Security Scan
Restore cache failed: Dependencies file is not found in /home/runner/work/chaoslabs/chaoslabs. Supported file pattern: go.sum
Build dashboard image
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/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build controller image
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/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build agent image
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/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/