Error: [vitest] No "getToolEntry" export is defined on the "@/lib/copilot/tool-executor" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/copilot/tool-executor"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:284:17 ❯ Object.get ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:330:16 ❯ handleCallPhase lib/copilot/request/handlers/tool.ts:194:24 ❯ handleToolEvent lib/copilot/request/handlers/tool.ts:81:3 ❯ Object.tool lib/copilot/request/handlers/index.ts:19:56 ❯ lib/copilot/request/handlers/handlers.test.ts:392:23 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 This error originated in "lib/copilot/request/handlers/handlers.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 "does not execute a tool if a terminal tool_result arrives before local execution starts". 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.

Error: [vitest] No "getToolEntry" export is defined on the "@/lib/copilot/tool-executor" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/copilot/tool-executor"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:284:17 ❯ Object.get ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:330:16 ❯ handleCallPhase lib/copilot/request/handlers/tool.ts:194:24 ❯ handleToolEvent lib/copilot/request/handlers/tool.ts:81:3 ❯ Object.tool lib/copilot/request/handlers/index.ts:19:56 ❯ lib/copilot/request/handlers/handlers.test.ts:357:23 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 This error originated in "lib/copilot/request/handlers/handlers.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 "still executes the tool when async row upsert fails". 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.

Error: [vitest] No "getToolEntry" export is defined on the "@/lib/copilot/tool-executor" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/copilot/tool-executor"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:284:17 ❯ Object.get ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:330:16 ❯ handleCallPhase lib/copilot/request/handlers/tool.ts:194:24 ❯ handleToolEvent lib/copilot/request/handlers/tool.ts:81:3 ❯ Object.tool lib/copilot/request/handlers/index.ts:19:56 ❯ lib/copilot/request/handlers/handlers.test.ts:336:23 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 This error originated in "lib/copilot/request/handlers/handlers.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 "does not replace an in-flight pending promise on duplicate tool_call". 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.

Error: [vitest] No "getToolEntry" export is defined on the "@/lib/copilot/tool-executor" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/copilot/tool-executor"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:284:17 ❯ Object.get ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:330:16 ❯ handleCallPhase lib/copilot/request/handlers/tool.ts:194:24 ❯ handleToolEvent lib/copilot/request/handlers/tool.ts:81:3 ❯ Object.tool lib/copilot/request/handlers/index.ts:19:56 ❯ lib/copilot/request/handlers/handlers.test.ts:285:23 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 This error originated in "lib/copilot/request/handlers/handlers.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 "marks an in-flight tool as cancelled when aborted mid-execution". 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.

Error: [vitest] No "getToolEntry" export is defined on the "@/lib/copilot/tool-executor" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/copilot/tool-executor"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:284:17 ❯ Object.get ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:330:16 ❯ handleCallPhase lib/copilot/request/handlers/tool.ts:194:24 ❯ handleToolEvent lib/copilot/request/handlers/tool.ts:81:3 ❯ Object.tool lib/copilot/request/handlers/index.ts:19:56 ❯ lib/copilot/request/handlers/handlers.test.ts:267:23 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:752:20 This error originated in "lib/copilot/request/handlers/handlers.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 "marks an in-flight tool as cancelled when aborted mid-execution". 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.

Error: [vitest] No "getToolEntry" export is defined on the "@/lib/copilot/tool-executor" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/copilot/tool-executor"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:284:17 ❯ Object.get ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:330:16 ❯ handleCallPhase lib/copilot/request/handlers/tool.ts:194:24 ❯ handleToolEvent lib/copilot/request/handlers/tool.ts:81:3 ❯ Object.tool lib/copilot/request/handlers/index.ts:19:56 ❯ lib/copilot/request/handlers/handlers.test.ts:265:23 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 This error originated in "lib/copilot/request/handlers/handlers.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 "skips duplicate tool_call after result". 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.

Error: [vitest] No "getToolEntry" export is defined on the "@/lib/copilot/tool-executor" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/copilot/tool-executor"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:284:17 ❯ Object.get ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:330:16 ❯ handleCallPhase lib/copilot/request/handlers/tool.ts:194:24 ❯ handleToolEvent lib/copilot/request/handlers/tool.ts:81:3 ❯ Object.tool lib/copilot/request/handlers/index.ts:29:56 ❯ lib/copilot/request/handlers/handlers.test.ts:227:28 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 This error originated in "lib/copilot/request/handlers/handlers.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 "routes subagent tool calls using the event scope parent tool call id". 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.

Error: [vitest] No "getToolEntry" export is defined on the "@/lib/copilot/tool-executor" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/copilot/tool-executor"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:284:17 ❯ Object.get ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:330:16 ❯ handleCallPhase lib/copilot/request/handlers/tool.ts:194:24 ❯ handleToolEvent lib/copilot/request/handlers/tool.ts:81:3 ❯ Object.tool lib/copilot/request/handlers/index.ts:29:56 ❯ lib/copilot/request/handlers/handlers.test.ts:158:28 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:752:20 This error originated in "lib/copilot/request/handlers/handlers.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 "updates stored params when a subagent generating event is followed by the final tool call". 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.

Error: [vitest] No "getToolEntry" export is defined on the "@/lib/copilot/tool-executor" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/copilot/tool-executor"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:284:17 ❯ Object.get ../../node_modules/vitest/dist/chunks/execute.B7h3T_Hc.js:330:16 ❯ handleCallPhase lib/copilot/request/handlers/tool.ts:194:24 ❯ handleToolEvent lib/copilot/request/handlers/tool.ts:81:3 ❯ Object.tool lib/copilot/request/handlers/index.ts:19:56 ❯ lib/copilot/request/handlers/handlers.test.ts:91:23 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ ../../node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 This error originated in "lib/copilot/request/handlers/handlers.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 "executes tool_call and emits tool_result". 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.

sim#test: command (/home/runner/_work/sim/sim/apps/sim) /home/runner/.bun/bin/bun run test exited (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/checkout@v4, actions/setup-node@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/

Skipping sticky disk commit due to previous step failures

- Step: unknown (failed)

Found 2 failed/cancelled steps in previous workflow steps

Skipping sticky disk commit due to previous step failures

- Step: unknown (failed)