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/OnUncaughtException/test.ts:8:3

AssertionError: expected null not to be null ❯ suites/public-api/OnUncaughtException/test.ts:15:25 ❯ ChildProcess.exithandler node:child_process:414:7 ❯ 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/OnUncaughtException/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 close process on uncaught error with no additional listeners registered". 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.

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. 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: actions/cache@v4, dkhunt27/action-nx-affected-list@v6.1. 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/

Identifier 'beforeEach' is imported but never used.

Identifier 'afterEach' is imported but never used.

Identifier 'vi' is imported but never used.

Identifier 'beforeEach' is imported but never used.

Identifier 'afterEach' is imported but never used.

Identifier 'hasSpanStreamingEnabled' is imported but never used.

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: dev-packages/bun-integration-tests/expect.ts, dev-packages/bun-integration-tests/suites/basic/test.ts, dev-packages/bun-integration-tests/suites/hono-sdk/index.ts, dev-packages/bun-integration-tests/suites/hono-sdk/test.ts, packages/hono/package.json, packages/hono/rollup.npm.config.mjs, packages/hono/src/bun/middleware.ts, packages/hono/src/bun/sdk.ts, packages/hono/src/index.bun.ts, packages/hono/test/bun/middleware.test.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js This usually indicates a path format mismatch between your coverage tool and the repository.

Please ensure your test framework is generating JUnit XML output.

No JUnit XML files found matching pattern: **/*.junit.xml

No files found matching pattern: **/*.junit.xml