dev: bump @babel/plugin-transform-modules-systemjs from 7.29.0 to 7.29.4 #2352
dependabot[bot]console-e2e.yml
on: pull_request
Determine if run is required
18s
Matrix: Main frontend end-to-end tests (Chrome)
Write result cache
0s
Annotations
11 errors and 7 warnings
|
Determine if run is required
Process completed with exit code 1.
|
|
Main frontend end-to-end tests (Chrome) (1)
Process completed with exit code 2.
|
|
Main frontend end-to-end tests (Chrome) (1)
no matching workflow run found with any artifacts?
|
|
Main frontend end-to-end tests (Chrome) (3)
Process completed with exit code 2.
|
|
Main frontend end-to-end tests (Chrome) (3)
no matching workflow run found with any artifacts?
|
|
Main frontend end-to-end tests (Chrome) (4)
Cypress tests: 1 failed
|
|
Main frontend end-to-end tests (Chrome) (4)
Process completed with exit code 2.
|
|
Main frontend end-to-end tests (Chrome) (4)
no matching workflow run found with any artifacts?
|
|
Main frontend end-to-end tests (Chrome) (2)
The strategy configuration was canceled because "end-to-end._4" failed
|
|
Main frontend end-to-end tests (Chrome) (2)
Process completed with exit code 2.
|
|
Main frontend end-to-end tests (Chrome) (2)
no matching workflow run found with any artifacts?
|
|
Run preparations
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/setup-go@v5, actions/setup-node@v4. 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/
|
|
Cross-browser smoke tests (Firefox 141.0)
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/setup-go@v5, actions/setup-node@v4. 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/
|
|
Main frontend end-to-end tests (Chrome) (1)
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/setup-go@v5, actions/setup-node@v4. 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/
|
|
Main frontend end-to-end tests (Chrome) (3)
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/setup-go@v5, actions/setup-node@v4. 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/
|
|
Main frontend end-to-end tests (Chrome) (4)
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/setup-go@v5, actions/setup-node@v4. 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/
|
|
Main frontend end-to-end tests (Chrome) (4)
No files were found with the provided path: .cache/.failed-specs-*.txt. No artifacts will be uploaded.
|
|
Main frontend end-to-end tests (Chrome) (2)
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/setup-go@v5, actions/setup-node@v4. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-files
|
113 MB |
sha256:6053cd11ec6413c264520ac90c2358a1afe4c7a92bca9dd56a1ba7c2d5d510d0
|
|
|
cypress-screenshots
|
2.58 KB |
sha256:80937bb687ce7e8fbfdb297ec8822b518dfde55c9bdd691781ebb7bc012ee8c8
|
|
|
logs
|
575 KB |
sha256:19cf23b6278cb98c9b1205d712fb07a1f6dfd7699631fce1b5f3cf93af199d29
|
|