Process completed with exit code 1.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:44:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:55:12 ❯ ChildProcess.exithandler node:child_process:424:5 ❯ ChildProcess.emit node:events:519:28 ❯ maybeClose node:internal/child_process:1101:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:304:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:44:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:55:12 ❯ ChildProcess.exithandler node:child_process:424:5 ❯ ChildProcess.emit node:events:509:28 ❯ maybeClose node:internal/child_process:1124:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:306:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:44:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:55:12 ❯ ChildProcess.exithandler node:child_process:430:5 ❯ ChildProcess.emit node:events:517:28 ❯ maybeClose node:internal/child_process:1098:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:303:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:44:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:55:12 ❯ ChildProcess.exithandler node:child_process:424:5 ❯ ChildProcess.emit node:events:509:20 ❯ maybeClose node:internal/child_process:1108:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:305:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:44:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:55:12 ❯ ChildProcess.exithandler node:child_process:430:5 ❯ ChildProcess.emit node:events:524:28 ❯ maybeClose node:internal/child_process:1104:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:304:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:44:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:55:12 ❯ ChildProcess.exithandler node:child_process:424:5 ❯ ChildProcess.emit node:events:509:28 ❯ maybeClose node:internal/child_process:1124:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:306:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:45:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:56:12 ❯ ChildProcess.exithandler node:child_process:424:5 ❯ ChildProcess.emit node:events:509:28 ❯ maybeClose node:internal/child_process:1124:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:306:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:45:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:56:12 ❯ ChildProcess.exithandler node:child_process:424:5 ❯ ChildProcess.emit node:events:509:20 ❯ maybeClose node:internal/child_process:1108:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:305:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:45:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:56:12 ❯ ChildProcess.exithandler node:child_process:430:5 ❯ ChildProcess.emit node:events:517:28 ❯ maybeClose node:internal/child_process:1098:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:303:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:45:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:56:12 ❯ ChildProcess.exithandler node:child_process:424:5 ❯ ChildProcess.emit node:events:519:28 ❯ maybeClose node:internal/child_process:1101:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:304:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:45:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:56:12 ❯ ChildProcess.exithandler node:child_process:430:5 ❯ ChildProcess.emit node:events:524:28 ❯ maybeClose node:internal/child_process:1104:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:304:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:45:3

AssertionError: expected 'test rejection\n' to be 'Error: test rejection\n at Object.…' // Object.is equality - Expected + Received - Error: test rejection - at Object.<anonymous> + test rejection ❯ suites/public-api/onUnhandledRejectionIntegration/test.ts:56:12 ❯ ChildProcess.exithandler node:child_process:424:5 ❯ ChildProcess.emit node:events:509:28 ❯ maybeClose node:internal/child_process:1124:16 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:306:5 This error originated in "suites/public-api/onUnhandledRejectionIntegration/test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not close process on unhandled rejection in strict mode". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

The job has exceeded the maximum execution time of 15m0s

The operation was canceled.

The job has exceeded the maximum execution time of 15m0s

The operation was canceled.

Process completed with exit code 1.

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/

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/

4 passed (2.5s)

3 skipped 17 passed (2.3s)

3 passed (3.8s)

3 passed (3.9s)

3 passed (3.7s)

4 passed (2.9s)

12 passed (6.8s)

4 passed (7.8s)

2 passed (4.4s)

3 passed (8.8s)

3 passed (2.9s)

1 passed (2.4s)

18 passed (4.7s)

9 passed (10.4s)

1 skipped 61 passed (5.2s)

10 passed (10.7s)

3 passed (4.2s)

1 passed (6.5s)

1 skipped 61 passed (4.1s)

2 passed (3.6s)

5 passed (18.1s)

4 passed (7.7s)

8 passed (6.4s)

4 passed (2.5s)

7 passed (8.9s)

11 passed (5.5s)

11 passed (5.9s)

9 passed (11.6s)

5 passed (9.2s)

11 passed (6.5s)

11 passed (6.8s)

3 skipped 17 passed (2.8s)

7 passed (10.1s)

5 passed (7.9s)

1 skipped 61 passed (5.1s)

7 passed (6.6s)

3 passed (5.6s)

15 passed (10.8s)

24 passed (15.7s)

23 passed (14.5s)

22 passed (10.1s)

12 passed (5.2s)

10 passed (5.4s)

10 passed (5.8s)

16 passed (28.7s)

29 passed (28.6s)

3 passed (5.9s)

12 skipped 1 passed (3.4s)

1 skipped 14 passed (12.3s)

3 passed (2.3s)

11 passed (2.2s)

7 passed (8.4s)

13 passed (28.4s)

4 passed (14.6s)

4 passed (3.7s)

7 passed (15.9s)

7 passed (27.3s)

13 passed (28.7s)

9 passed (11.2s)

9 passed (11.5s)

2 skipped 20 passed (24.6s)

53 passed (26.4s)

3 passed (2.7s)

2 passed (24.3s)

9 passed (11.6s)

9 passed (11.6s)

11 passed (14.5s)

11 passed (14.9s)

12 passed (8.6s)

5 passed (9.1s)

18 passed (18.2s)

9 passed (11.2s)

8 passed (6.3s)

7 passed (28.3s)

12 skipped 1 passed (2.9s)

14 passed (24.6s)

18 passed (19.1s)

11 passed (18.9s)

3 passed (15.6s)

3 passed (9.7s)

13 passed (22.7s)

3 passed (15.8s)

3 passed (9.7s)

16 passed (24.2s)

12 skipped 1 passed (4.7s)

2 skipped 20 passed (24.9s)

14 skipped 12 passed (20.9s)

1 skipped 12 passed (6.0s)

7 passed (26.9s)

4 passed (3.2s)

8 passed (10.2s)

10 passed (37.0s)

12 passed (19.8s)

12 skipped 1 passed (3.9s)

10 passed (37.5s)

9 passed (10.3s)

14 skipped 12 passed (22.0s)

17 passed (56.1s)

4 skipped 10 passed (23.3s)

4 skipped 10 passed (6.9s)

9 passed (7.2s)

3 passed (32.9s)

3 passed (4.6s)

2 skipped 14 passed (1.2m)

4 skipped 10 passed (33.1s)

2 skipped 12 passed (7.0s)

3 passed (35.6s)

3 passed (9.9s)

13 passed (43.2s)

13 passed (9.5s)

4 skipped 10 passed (29.3s)

2 skipped 12 passed (7.0s)

4 passed (34.0s)

4 passed (8.3s)

3 skipped 27 passed (40.8s)

30 passed (12.2s)

6 skipped 6 passed (35.0s)

12 passed (51.6s)

5 passed (42.0s)

5 passed (10.9s)

8 passed (2.2s)

4 passed (18.3s)

51 passed (1.0m)

13 skipped 30 passed (1.7m)

2 skipped 41 passed (1.1m)

13 skipped 30 passed (1.7m)

2 skipped 41 passed (1.1m)

2 skipped 29 passed (2.0m)

2 skipped 29 passed (38.2s)

4 passed (20.8s)

2 skipped 32 passed (2.4m)

2 skipped 32 passed (1.1m)

5 skipped 29 passed (2.0m)

6 skipped 28 passed (1.1m)

9 skipped 34 passed (2.7m)

2 skipped 41 passed (1.0m)

9 skipped 34 passed (2.7m)

2 skipped 41 passed (1.0m)

2 skipped 32 passed (2.9m)