Skip to content

Merge pull request #201 from Qoder-Undefined/Zone #73

Merge pull request #201 from Qoder-Undefined/Zone

Merge pull request #201 from Qoder-Undefined/Zone #73

Triggered via push April 27, 2026 11:00
Status Failure
Total duration 1m 36s
Artifacts 5

test.yml

on: push
Performance Tests
47s
Performance Tests
Matrix: E2E Tests
Matrix: Unit & Integration Tests
Fit to window
Zoom out
Zoom in

Annotations

63 errors and 7 warnings
Performance Tests: src/app/compare/page.tsx#L322
Identifier expected.
Performance Tests: src/app/compare/page.tsx#L321
Expression expected.
Performance Tests: src/app/compare/page.tsx#L318
Unexpected token. Did you mean `{'}'}` or `}`?
Performance Tests: src/app/compare/page.tsx#L317
Unexpected token. Did you mean `{'>'}` or `>`?
Performance Tests: src/app/compare/page.tsx#L314
Unexpected token. Did you mean `{'>'}` or `>`?
Performance Tests: src/app/compare/page.tsx#L313
Unexpected token. Did you mean `{'>'}` or `>`?
Performance Tests: src/app/compare/page.tsx#L312
Expression expected.
Performance Tests: src/app/compare/page.tsx#L311
Unexpected token. Did you mean `{'>'}` or `>`?
Performance Tests: src/app/compare/page.tsx#L301
JSX element 'parameter' has no corresponding closing tag.
Performance Tests: src/app/compare/page.tsx#L300
Declaration or statement expected.
Unit & Integration Tests (20.x): src/app/compare/page.tsx#L318
Unexpected token. Did you mean `{'}'}` or `}`?
Unit & Integration Tests (20.x): src/app/compare/page.tsx#L317
Unexpected token. Did you mean `{'>'}` or `>`?
Unit & Integration Tests (20.x): src/app/compare/page.tsx#L314
Unexpected token. Did you mean `{'>'}` or `>`?
Unit & Integration Tests (20.x): src/app/compare/page.tsx#L313
Unexpected token. Did you mean `{'>'}` or `>`?
Unit & Integration Tests (20.x): src/app/compare/page.tsx#L311
Unexpected token. Did you mean `{'>'}` or `>`?
Unit & Integration Tests (20.x): src/app/compare/page.tsx#L301
JSX element 'parameter' has no corresponding closing tag.
Unit & Integration Tests (20.x): src/app/compare/page.tsx#L300
Declaration or statement expected.
Unit & Integration Tests (18.x)
The strategy configuration was canceled because "unit-tests._20_x" failed
Unit & Integration Tests (18.x): src/app/compare/page.tsx#L318
Unexpected token. Did you mean `{'}'}` or `}`?
Unit & Integration Tests (18.x): src/app/compare/page.tsx#L317
Unexpected token. Did you mean `{'>'}` or `>`?
Unit & Integration Tests (18.x): src/app/compare/page.tsx#L314
Unexpected token. Did you mean `{'>'}` or `>`?
Unit & Integration Tests (18.x): src/app/compare/page.tsx#L313
Unexpected token. Did you mean `{'>'}` or `>`?
Unit & Integration Tests (18.x): src/app/compare/page.tsx#L311
Unexpected token. Did you mean `{'>'}` or `>`?
Unit & Integration Tests (18.x): src/app/compare/page.tsx#L301
JSX element 'parameter' has no corresponding closing tag.
Unit & Integration Tests (18.x): src/app/compare/page.tsx#L300
Declaration or statement expected.
E2E Tests (chromium): src/app/compare/page.tsx#L322
Identifier expected.
E2E Tests (chromium): src/app/compare/page.tsx#L321
Expression expected.
E2E Tests (chromium): src/app/compare/page.tsx#L318
Unexpected token. Did you mean `{'}'}` or `}`?
E2E Tests (chromium): src/app/compare/page.tsx#L317
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (chromium): src/app/compare/page.tsx#L314
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (chromium): src/app/compare/page.tsx#L313
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (chromium): src/app/compare/page.tsx#L312
Expression expected.
E2E Tests (chromium): src/app/compare/page.tsx#L311
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (chromium): src/app/compare/page.tsx#L301
JSX element 'parameter' has no corresponding closing tag.
E2E Tests (chromium): src/app/compare/page.tsx#L300
Declaration or statement expected.
E2E Tests (firefox)
The strategy configuration was canceled because "e2e-tests.chromium" failed
E2E Tests (firefox): src/app/compare/page.tsx#L322
Identifier expected.
E2E Tests (firefox): src/app/compare/page.tsx#L321
Expression expected.
E2E Tests (firefox): src/app/compare/page.tsx#L318
Unexpected token. Did you mean `{'}'}` or `}`?
E2E Tests (firefox): src/app/compare/page.tsx#L317
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (firefox): src/app/compare/page.tsx#L314
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (firefox): src/app/compare/page.tsx#L313
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (firefox): src/app/compare/page.tsx#L312
Expression expected.
E2E Tests (firefox): src/app/compare/page.tsx#L311
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (firefox): src/app/compare/page.tsx#L301
JSX element 'parameter' has no corresponding closing tag.
E2E Tests (firefox): src/app/compare/page.tsx#L300
Declaration or statement expected.
E2E Tests (webkit)
The strategy configuration was canceled because "e2e-tests.chromium" failed
E2E Tests (webkit): src/app/compare/page.tsx#L322
Identifier expected.
E2E Tests (webkit): src/app/compare/page.tsx#L321
Expression expected.
E2E Tests (webkit): src/app/compare/page.tsx#L318
Unexpected token. Did you mean `{'}'}` or `}`?
E2E Tests (webkit): src/app/compare/page.tsx#L317
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (webkit): src/app/compare/page.tsx#L314
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (webkit): src/app/compare/page.tsx#L313
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (webkit): src/app/compare/page.tsx#L312
Expression expected.
E2E Tests (webkit): src/app/compare/page.tsx#L311
Unexpected token. Did you mean `{'>'}` or `>`?
E2E Tests (webkit): src/app/compare/page.tsx#L301
JSX element 'parameter' has no corresponding closing tag.
E2E Tests (webkit): src/app/compare/page.tsx#L300
Declaration or statement expected.
Performance 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-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/
Performance Tests
No files were found with the provided path: .next/analyze/ performance-results/. No artifacts will be uploaded.
Unit & Integration Tests (20.x)
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-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/
Unit & Integration Tests (18.x)
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-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/
E2E Tests (chromium)
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-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/
E2E Tests (firefox)
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-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/
E2E Tests (webkit)
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-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/

Artifacts

Produced during runtime
Name Size Digest
e2e-results-chromium Expired
15.4 KB
sha256:d1223980848750cacf9344501afff95af5dc7bddf83e9c64b326ff1bfdde0feb
e2e-results-firefox Expired
15.4 KB
sha256:2002efb1979e7ee580202365bcb0d8aa64fe03cf2cc12e65761fe0c6aeb8a451
e2e-results-webkit Expired
15.4 KB
sha256:d1223980848750cacf9344501afff95af5dc7bddf83e9c64b326ff1bfdde0feb
test-results-18.x Expired
15.4 KB
sha256:56dd16dd2d9a2ca9f3a9c579d24d18f67c534aa84502bf95bd4860fa286b40d0
test-results-20.x Expired
15.4 KB
sha256:6f30795ffb92f5eff2839808530bfea5686c8135bc800448ad6c0aba6de313b3