Skip to content
End-to-end Tests

TTGC LBS CUPS Claimer #2263

Sign in to view logs

TTGC LBS CUPS Claimer

TTGC LBS CUPS Claimer #2263

Triggered via pull request March 26, 2026 14:24
@vlasebianvlasebian
synchronize #7813
feat/ttgc-lbs-cups-claim
Status Failure
Total duration 13m 55s
Artifacts 2

console-e2e.yml

on: pull_request
Determine if run is required
18s
Determine if run is required
Run preparations
9m 3s
Run preparations
Matrix: Main frontend end-to-end tests (Chrome)
Cross-browser smoke tests (Firefox 141.0)
4m 24s
Cross-browser smoke tests (Firefox 141.0)
Write result cache
0s
Write result cache
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 11 warnings
Determine if run is required
Process completed with exit code 1.
Main frontend end-to-end tests (Chrome) (4)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Main frontend end-to-end tests (Chrome) (4)
Could not find Cypress test run results
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)
Could not find Cypress test run results
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?
Main frontend end-to-end tests (Chrome) (3)
The strategy configuration was canceled because "end-to-end._4" failed
Main frontend end-to-end tests (Chrome) (3)
The operation was canceled.
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) (1)
The strategy configuration was canceled because "end-to-end._4" failed
Main frontend end-to-end tests (Chrome) (1)
The operation was canceled.
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?
Determine if run is required
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 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 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/upload-artifact@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/download-artifact@v5, actions/setup-go@v5, actions/setup-node@v4, actions/upload-artifact@v4, cypress-io/github-action@v6, dawidd6/action-download-artifact@v11. 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) (4)
No files were found with the provided path: cypress/screenshots. 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/download-artifact@v5, actions/setup-go@v5, actions/setup-node@v4, actions/upload-artifact@v4, cypress-io/github-action@v6, dawidd6/action-download-artifact@v11. 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) (2)
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)
No files were found with the provided path: cypress/screenshots. No artifacts will be uploaded.
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/download-artifact@v5, actions/setup-go@v5, actions/setup-node@v4, cypress-io/github-action@v6, dawidd6/action-download-artifact@v11. 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/
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/download-artifact@v5, actions/setup-go@v5, actions/setup-node@v4, cypress-io/github-action@v6, dawidd6/action-download-artifact@v11. 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/
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/download-artifact@v5, actions/setup-go@v5, actions/setup-node@v4, cypress-io/github-action@v6. 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/

Artifacts

Produced during runtime
Name Size Digest
build-files
111 MB
sha256:c56dacc8df163a0c1620818b19afa1e9470d8a38908be396bca654e6ed12cbe3
logs
2.25 KB
sha256:2f74e04ed549d9a16e311ccd098da58c12b42bfc554f98bdeaa23b98c65359d1