Skip to content

test(files): reload tagger in TagServiceTest to avoid flaky cache state #55935

test(files): reload tagger in TagServiceTest to avoid flaky cache state

test(files): reload tagger in TagServiceTest to avoid flaky cache state #55935

Triggered via pull request June 8, 2026 16:05
Status Failure
Total duration 1h 17m 57s
Artifacts 15

cypress.yml

on: pull_request
Matrix: cypress
cypress-summary
7s
cypress-summary
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 15 warnings
runner 8
Cypress tests: 1 failed
runner 5
Cypress tests: 1 failed
runner 7
Cypress tests: 2 failed
runner 1
Cypress tests: 1 failed
runner 3
Cypress tests: 1 failed
runner 2
Cypress tests: 8 failed
cypress-summary
Process completed with exit code 1.
init
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4, buildjet/cache/save@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4, skjnldsv/read-package-engines-version-actions@06d6baf7d8f41934ab630e97d9e6c0bc9c9ac5e4. 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/
runner 8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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/
runner 5
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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/
runner 7
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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/
runner 4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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/
runner 6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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/
runner 9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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/
runner 9
No files were found with the provided path: cypress/snapshots cypress/videos. No artifacts will be uploaded.
runner 0
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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/
runner 1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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/
runner setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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/
runner setup
Docker network rm failed with exit code 1
runner setup
No files were found with the provided path: cypress/snapshots cypress/videos. No artifacts will be uploaded.
runner 3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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/
runner 2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4. 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
nc_data_1
5.09 MB
sha256:b2b0515217a5c94805437bbfeebf75239b5363112eeb330b30f217558b0ae396
nc_data_2
8.65 MB
sha256:81e8f0a913d3858995fddf5d01db3bdc32b9210277a92c3460ca9b852474af81
nc_data_3
5.42 MB
sha256:f51dce1f4a74cfac0eee49995cd2148d1ebbf563628f40dc802a5fbeb19d5ef6
nc_data_5
3.29 MB
sha256:7425773bd7e56a2e583877902c1c408210a8b04a5e01ab5198745bae5ef56679
nc_data_7
1.2 MB
sha256:05a71f63fa7e18539943e8076655aae0ad11951e0105257ffd5c85038f33cbf6
nc_data_8
3.31 MB
sha256:0041aa4e737fb6b30f24a69208e82b7d7a6cdc09ea6224c718a08fa140346634
snapshots_0
40.3 KB
sha256:9c45181eb1e1c418cf6304caf5b17c21fecbfc1168ab173806b0beed808806c2
snapshots_1
1.29 MB
sha256:8df7fd1856da888df4826d9a87e00af9a28bf909299787408dd75a78f0209c75
snapshots_2
7.9 MB
sha256:4297d96e1c37a6055e9a143e7f7f0d2d9023af395c9a3cee7f090c847fd5956a
snapshots_3
1.34 MB
sha256:6882804fa13295193dac8e29406b281864564ddaeea9d40af0f56c293657df6d
snapshots_4
128 KB
sha256:4596122bc463703f250ba712fb55912654030efca9ace134c1d4079f86aece15
snapshots_5
985 KB
sha256:2e155af954f911c80aff945b9d1a7945bcd9b1acc89a7a48917856f12cfa6a9a
snapshots_6
795 KB
sha256:2b193850695093b7c2938ffad4c3798d7ad84449533e62bfffa490de3e665c78
snapshots_7
2.51 MB
sha256:598f5b1129aa70e04b17ec76841175e2fa4a2c52cf33fc264815b7ce372fa6d7
snapshots_8
1.01 MB
sha256:8d9034489a8be2ac148df8be8e1a876b0c863af402b3ce1a8d457642494906c2