1) [chromium] › tests/orpc-error.test.ts:4:1 › should capture server-side orpc error ───────────── Test timeout of 30000ms exceeded.

2) [chromium] › tests/trpc-mutation.test.ts:4:1 › should create transaction with trpc input for mutation Test timeout of 30000ms exceeded.

1) [chromium] › tests/trpc-error.test.ts:4:1 › should capture error with trpc context ──────────── Test timeout of 30000ms exceeded.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

1) [chromium] › suites/profiling/traceLifecycleMode_overlapping-spans/test.ts:33:11 › sends profile envelope in trace mode (single chunk for overlapping spans) Error: expect(received).toHaveProperty(path) Expected path: "abs_path" Received path: [] Received value: {"function": "now"} at profiling/test-utils.ts:104 102 | // Some browser functions (fetch, setTimeout) may not have file locations 103 | if (frame.function !== 'fetch' && frame.function !== 'setTimeout') { > 104 | expect(frame).toHaveProperty('abs_path'); | ^ 105 | expect(frame).toHaveProperty('lineno'); 106 | expect(frame).toHaveProperty('colno'); 107 | expect(typeof frame.abs_path).toBe('string'); at validateProfile (/home/runner/work/sentry-javascript/sentry-javascript/dev-packages/browser-integration-tests/suites/profiling/test-utils.ts:104:21) at /home/runner/work/sentry-javascript/sentry-javascript/dev-packages/browser-integration-tests/suites/profiling/traceLifecycleMode_overlapping-spans/test.ts:59:20

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

The operation was canceled.

Process completed with exit code 1.

Canceling since a higher priority waiting request for CI: Build & Test-chargome/feat/applicationkey-build-options exists

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2. 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/

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: packages/astro/src/integration/index.ts, packages/astro/test/integration/index.test.ts, packages/core/src/build-time-plugins/buildTimeOptionsBase.ts, packages/nuxt/src/vite/sourceMaps.ts, packages/nuxt/test/vite/sourceMaps.test.ts, packages/react-router/src/vite/makeCustomSentryVitePlugins.ts, packages/react-router/test/vite/makeCustomSentryVitePlugins.test.ts, packages/sveltekit/test/vite/sentrySvelteKitPlugins.test.ts Sample coverage paths: ./mute.js, /home/runner/work/sentry-javascript/sentry-javascript/packages/browser/src/client.ts, /home/runner/work/sentry-javascript/sentry-javascript/packages/browser/src/debug-build.ts This usually indicates a path format mismatch between your coverage tool and the repository.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./dev-packages/size-limit-gh-action. 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/

2 passed (2.5s)

1 passed (2.2s)

3 passed (2.8s)

3 skipped 17 passed (2.7s)

3 passed (3.7s)

11 passed (2.8s)

8 passed (2.7s)

3 passed (2.8s)

4 passed (7.7s)

1 passed (5.5s)

13 passed (12.7s)

2 passed (4.5s)

5 passed (12.1s)

12 passed (5.8s)

3 skipped 17 passed (2.4s)

5 passed (11.9s)

4 passed (4.7s)

4 passed (2.5s)

3 passed (5.4s)

1 passed (3.6s)

24 passed (15.3s)

4 passed (7.8s)

1 passed (6.4s)

11 passed (6.4s)

11 passed (6.8s)

1 passed (5.5s)

3 passed (3.9s)

7 passed (11.2s)

1 passed (6.2s)

2 passed (7.3s)

5 passed (18.0s)

4 passed (4.3s)

15 passed (10.5s)

3 passed (2.9s)

2 passed (3.6s)

8 passed (3.4s)

8 passed (3.4s)

5 passed (8.4s)

22 passed (11.5s)

4 passed (2.5s)

7 passed (8.9s)

3 passed (3.7s)

3 passed (18.8s)

4 passed (2.7s)

18 passed (10.1s)

3 passed (13.8s)

1 passed (3.6s)

3 passed (6.6s)

1 passed (3.6s)

3 passed (7.7s)

3 passed (5.3s)

12 passed (9.5s)

43 passed (4.6s)

43 passed (3.6s)

11 passed (5.1s)

11 passed (5.7s)

10 passed (5.4s)

10 passed (5.8s)

3 passed (8.9s)

3 passed (15.8s)

5 passed (9.3s)

12 passed (6.8s)

11 passed (14.6s)

3 skipped 21 passed (18.2s)

3 passed (3.1s)

7 passed (8.7s)

4 passed (8.9s)

9 passed (12.2s)

23 passed (13.0s)

9 passed (10.0s)

5 passed (7.1s)

4 passed (8.9s)

10 passed (26.7s)

1 passed (3.6s)

1 passed (3.6s)

5 passed (8.0s)

13 passed (28.6s)

5 passed (9.0s)

9 passed (11.8s)

1 passed (4.7s)

7 passed (5.3s)

11 passed (15.7s)

29 passed (30.8s)

9 passed (12.2s)

43 passed (5.0s)

10 passed (28.1s)

18 passed (18.3s)

9 passed (11.7s)

8 passed (7.1s)

2 passed (22.5s)

2 skipped 20 passed (26.6s)

5 passed (10.4s)

9 passed (11.0s)

4 passed (8.7s)

5 passed (9.9s)

10 passed (38.2s)

7 passed (22.2s)

10 passed (27.7s)

12 skipped 1 passed (3.9s)

7 passed (25.8s)

7 passed (5.1s)

15 passed (20.1s)

13 passed (25.0s)

1 skipped 14 passed (14.3s)

10 passed (36.5s)

9 passed (12.7s)

12 skipped 1 passed (3.9s)

16 passed (29.8s)

16 passed (24.7s)

7 passed (26.5s)

13 passed (28.6s)

14 passed (25.5s)

18 passed (18.9s)

12 passed (28.4s)

11 passed (17.7s)

11 passed (17.8s)

10 passed (10.0s)

2 skipped 20 passed (26.2s)

3 passed (17.0s)

3 passed (10.9s)

4 passed (11.2s)

4 passed (17.9s)

4 passed (4.1s)

12 passed (28.2s)

12 passed (17.7s)

12 passed (17.7s)

1 skipped 12 passed (5.7s)

40 passed (19.1s)

12 passed (19.6s)

8 passed (10.3s)

9 passed (11.1s)

12 skipped 1 passed (4.8s)

4 passed (10.5s)

12 passed (28.7s)

8 passed (31.0s)

12 passed (28.0s)

12 passed (29.0s)

40 passed (20.8s)

12 passed (5.0s)

12 passed (28.5s)

11 passed (19.4s)

8 passed (8.1s)

3 passed (15.9s)

3 passed (9.6s)

8 passed (30.0s)

14 skipped 12 passed (22.2s)

12 skipped 1 passed (3.1s)

4 passed (10.5s)

2 skipped 14 passed (1.2m)

3 passed (5.2s)

5 passed (8.6s)

14 skipped 12 passed (22.7s)

3 skipped 27 passed (39.1s)

30 passed (12.6s)

9 passed (9.5s)

4 passed (34.5s)

4 passed (8.7s)

5 passed (43.7s)

5 passed (12.6s)

14 skipped 12 passed (22.6s)

4 skipped 10 passed (25.9s)

4 skipped 10 passed (7.2s)

4 skipped 10 passed (35.9s)

2 skipped 12 passed (7.0s)

1 flaky [chromium] › tests/orpc-error.test.ts:4:1 › should capture server-side orpc error ────────────── 2 passed (42.4s)

3 passed (7.8s)

3 skipped 27 passed (41.0s)

30 passed (14.6s)

4 skipped 10 passed (30.9s)

2 skipped 12 passed (6.9s)

3 passed (36.4s)

3 passed (10.8s)

17 passed (57.5s)

13 passed (49.4s)

13 passed (9.4s)

13 passed (48.6s)

13 passed (9.0s)

2 flaky [chromium] › tests/trpc-error.test.ts:4:1 › should capture error with trpc context ───────────── [chromium] › tests/trpc-mutation.test.ts:4:1 › should create transaction with trpc input for mutation 1 passed (39.8s)

3 passed (4.4s)

4 passed (19.5s)

2 skipped 48 passed (1.0m)

4 passed (18.2s)

51 passed (1.0m)

13 passed (50.0s)

13 passed (9.4s)

7 skipped 23 passed (11.1s)

5 skipped 25 passed (17.3s)

5 skipped 25 passed (11.0s)

8 skipped 22 passed (10.5s)

2 skipped 29 passed (1.2m)

2 skipped 29 passed (37.5s)

1 skipped 29 passed (18.8s)

4 passed (18.7s)

51 passed (1.0m)

4 skipped 26 passed (19.2s)

15 passed (24.4s)

483 skipped 190 passed (36.3s)

478 skipped 195 passed (37.0s)

482 skipped 191 passed (36.8s)

12 passed (1.2m)

12 passed (50.9s)

7 skipped 23 passed (8.7s)

7 skipped 36 passed (1.8m)

2 skipped 41 passed (1.1m)

43 passed (2.2m)

346 skipped 327 passed (1.5m)

7 skipped 36 passed (1.8m)

2 skipped 41 passed (1.1m)

7 skipped 36 passed (1.8m)

2 skipped 41 passed (1.1m)

2 skipped 29 passed (2.0m)

2 skipped 29 passed (37.0s)

5 skipped 29 passed (2.0m)

6 skipped 28 passed (1.1m)

2 skipped 29 passed (2.0m)

2 skipped 29 passed (37.0s)

1 skipped 168 passed (2.6m)

2 skipped 32 passed (2.5m)

2 skipped 32 passed (1.1m)

348 skipped 325 passed (1.5m)

3 skipped 165 passed (2.6m)

4 passed (24.0s)

9 skipped 34 passed (2.8m)

2 skipped 41 passed (1.1m)

9 skipped 34 passed (3.0m)

2 skipped 41 passed (1.1m)

9 skipped 34 passed (3.0m)

2 skipped 41 passed (1.0m)

1 failed [chromium] › suites/profiling/traceLifecycleMode_overlapping-spans/test.ts:33:11 › sends profile envelope in trace mode (single chunk for overlapping spans) 190 skipped 482 passed (3.9m)

2 skipped 32 passed (3.1m)

2 skipped 32 passed (1.1m)

195 skipped 478 passed (3.8m)