Skip to content

4745 implement start past report #17065

4745 implement start past report

4745 implement start past report #17065

Triggered via pull request June 16, 2026 15:06
Status Failure
Total duration 12m 12s
Artifacts 2

main.yaml

on: pull_request
check-nx-affected
1m 2s
check-nx-affected
build-backend  /  docker-build
2m 2s
build-backend / docker-build
build-dashboard-e2e  /  docker-build
2m 2s
build-dashboard-e2e / docker-build
build-administration  /  docker-build
2m 2s
build-administration / docker-build
check-backend-changes  /  check
10s
check-backend-changes / check
build-compliance  /  docker-build
2m 2s
build-compliance / docker-build
build-registration  /  docker-build
1m 57s
build-registration / docker-build
build-reporting  /  docker-build
1m 57s
build-reporting / docker-build
check-frontend-changes  /  check
6s
check-frontend-changes / check
build-dashboard  /  docker-build
2m 3s
build-dashboard / docker-build
trivy  /  analyze
31s
trivy / analyze
Matrix: codeql / analyze
test-administration-e2e  /  🧪 e2e tests chromium
8m 44s
test-administration-e2e / 🧪 e2e tests chromium
test-administration-e2e  /  happo-skip-not-affected
0s
test-administration-e2e / happo-skip-not-affected
test-backend  /  pythontests
8m 15s
test-backend / pythontests
test-compliance-e2e  /  🧪 e2e tests chromium
1m 54s
test-compliance-e2e / 🧪 e2e tests chromium
test-compliance-e2e  /  happo-skip-not-affected
0s
test-compliance-e2e / happo-skip-not-affected
test-registration-e2e  /  🧪 e2e tests chromium
6m 24s
test-registration-e2e / 🧪 e2e tests chromium
test-registration-e2e  /  happo-skip-not-affected
0s
test-registration-e2e / happo-skip-not-affected
test-reporting-e2e  /  happo-skip-not-affected
test-reporting-e2e / happo-skip-not-affected
test-reporting-e2e  /  🧪 e2e tests chromium
test-reporting-e2e / 🧪 e2e tests chromium
test-dashboard-e2e  /  happo-skip-not-affected
test-dashboard-e2e / happo-skip-not-affected
test-dashboard-e2e  /  🧪 e2e tests chromium
test-dashboard-e2e / 🧪 e2e tests chromium
test-code  /  nx-tests
11m 1s
test-code / nx-tests
test-code  /  yarn-audit
56s
test-code / yarn-audit
test-code  /  prek
3m 31s
test-code / prek
test-code  /  check-migrations
1m 3s
test-code / check-migrations
test-code  /  check-immutable-migrations
1m 2s
test-code / check-immutable-migrations
test-code  /  check-test-data
3m 21s
test-code / check-test-data
test-code  /  check-dev-data
3m 18s
test-code / check-dev-data
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 12 warnings
build-reporting / docker-build
Process completed with exit code 130.
test-code / yarn-audit
Process completed with exit code 1.
test-compliance-e2e / 🧪 e2e tests chromium
Process completed with exit code 1.
test-backend / pythontests
Process completed with exit code 2.
test-code / nx-tests
Process completed with exit code 1.
build-backend / docker-build
Unexpected input(s) 'install', valid inputs are ['version', 'driver', 'driver-opts', 'buildkitd-flags', 'buildkitd-config', 'buildkitd-config-inline', 'use', 'name', 'endpoint', 'platforms', 'append', 'keep-state', 'cache-binary', 'cleanup']
Default value for global ARG results in an empty or invalid base image name: bc_obps/Dockerfile#L7
InvalidDefaultArgInFrom: Default value for ARG dhi.io/python:${PYTHON_VERSION}-debian13-dev results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build-backend / docker-build
Unexpected input(s) 'install', valid inputs are ['version', 'driver', 'driver-opts', 'buildkitd-flags', 'buildkitd-config', 'buildkitd-config-inline', 'use', 'name', 'endpoint', 'platforms', 'append', 'keep-state', 'cache-binary', 'cleanup']
test-code / check-migrations
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
test-code / check-immutable-migrations
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
test-compliance-e2e / 🧪 e2e tests chromium
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
test-code / check-dev-data
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
test-code / check-test-data
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
test-code / prek
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
test-backend / pythontests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
test-registration-e2e / 🧪 e2e tests chromium
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
test-administration-e2e / 🧪 e2e tests chromium
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Artifacts

Produced during runtime
Name Size Digest
bcgov~cas-registration~KQ8GT7.dockerbuild
89.8 KB
sha256:0ba089ee726f8695740660bed6d931abd4b86aa13974b6cd9a3da89d1d3e38b3
trivy-results
12.1 KB
sha256:a7d91a9ac8ac50e0ddf8ca6a2df5a895c8ff9eb5e72e36e573e7754c43ab243a