Process completed with exit code 1.

AssertionError: expected { '0': 'pipe:[39789]', …(19) } to strictly equal { '0': 'pipe:[39789]', …(18) } - Expected + Received Object { "0": "pipe:[39789]", "1": "pipe:[39790]", "10": "pipe:[39804]", "11": "pipe:[39804]", "114": "pipe:[36857]", "117": "pipe:[36858]", "14": "pipe:[38310]", "15": "pipe:[38310]", "19": "pipe:[37319]", "2": "pipe:[39791]", "20": "pipe:[37319]", "23": "pipe:[38320]", "24": "pipe:[38320]", "27": "pipe:[39808]", "29": "pipe:[39808]", + "32": "/dev/ptmx", "4": "pipe:[38308]", "5": "pipe:[38308]", "6": "pipe:[38309]", "7": "pipe:[38309]", } ❯ onExit tests/index.test.ts:65:34 ❯ wrapper.ts:88:9 This error originated in "tests/index.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 "spawns and exits". 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.

AssertionError: expected { '0': 'pipe:[39789]', …(19) } to strictly equal { '0': 'pipe:[39789]', …(18) } - Expected + Received Object { "0": "pipe:[39789]", "1": "pipe:[39790]", "10": "pipe:[39804]", "11": "pipe:[39804]", "114": "pipe:[36857]", "117": "pipe:[36858]", "14": "pipe:[38310]", "15": "pipe:[38310]", "19": "pipe:[37319]", "2": "pipe:[39791]", "20": "pipe:[37319]", "23": "pipe:[38320]", "24": "pipe:[38320]", "27": "pipe:[39808]", "29": "pipe:[39808]", + "32": "/dev/ptmx", "4": "pipe:[38308]", "5": "pipe:[38308]", "6": "pipe:[38309]", "7": "pipe:[38309]", } ❯ onExit tests/index.test.ts:65:34 ❯ wrapper.ts:88:9 This error originated in "tests/index.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 "spawns and exits". 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.

AssertionError: expected { '0': 'pipe:[39789]', …(19) } to strictly equal { '0': 'pipe:[39789]', …(18) } - Expected + Received Object { "0": "pipe:[39789]", "1": "pipe:[39790]", "10": "pipe:[39804]", "11": "pipe:[39804]", "114": "pipe:[36857]", "117": "pipe:[36858]", "14": "pipe:[38310]", "15": "pipe:[38310]", "19": "pipe:[37319]", "2": "pipe:[39791]", "20": "pipe:[37319]", "23": "pipe:[38320]", "24": "pipe:[38320]", "27": "pipe:[39808]", "29": "pipe:[39808]", + "32": "/dev/ptmx", "4": "pipe:[38308]", "5": "pipe:[38308]", "6": "pipe:[38309]", "7": "pipe:[38309]", } ❯ onExit tests/index.test.ts:65:34 ❯ wrapper.ts:88:9 This error originated in "tests/index.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 "spawns and exits". 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.

AssertionError: expected { '0': 'pipe:[39789]', …(19) } to strictly equal { '0': 'pipe:[39789]', …(18) } - Expected + Received Object { "0": "pipe:[39789]", "1": "pipe:[39790]", "10": "pipe:[39804]", "11": "pipe:[39804]", "114": "pipe:[36857]", "117": "pipe:[36858]", "14": "pipe:[38310]", "15": "pipe:[38310]", "19": "pipe:[37319]", "2": "pipe:[39791]", "20": "pipe:[37319]", "23": "pipe:[38320]", "24": "pipe:[38320]", "27": "pipe:[39808]", "29": "pipe:[39808]", + "32": "/dev/ptmx", "4": "pipe:[38308]", "5": "pipe:[38308]", "6": "pipe:[38309]", "7": "pipe:[38309]", } ❯ onExit tests/index.test.ts:65:34 ❯ wrapper.ts:88:9 ❯ processTicksAndRejections node:internal/process/task_queues:95:5 This error originated in "tests/index.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 "spawns and exits". 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.

AssertionError: expected { '0': 'pipe:[39789]', …(19) } to strictly equal { '0': 'pipe:[39789]', …(18) } - Expected + Received Object { "0": "pipe:[39789]", "1": "pipe:[39790]", "10": "pipe:[39804]", "11": "pipe:[39804]", "114": "pipe:[36857]", "117": "pipe:[36858]", "14": "pipe:[38310]", "15": "pipe:[38310]", "19": "pipe:[37319]", "2": "pipe:[39791]", "20": "pipe:[37319]", "23": "pipe:[38320]", "24": "pipe:[38320]", "27": "pipe:[39808]", "29": "pipe:[39808]", + "32": "/dev/ptmx", "4": "pipe:[38308]", "5": "pipe:[38308]", "6": "pipe:[38309]", "7": "pipe:[38309]", } ❯ onExit tests/index.test.ts:65:34 ❯ wrapper.ts:88:9 ❯ processTicksAndRejections node:internal/process/task_queues:95:5 This error originated in "tests/index.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 "spawns and exits". 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.

AssertionError: expected { '0': 'pipe:[39789]', …(19) } to strictly equal { '0': 'pipe:[39789]', …(18) } - Expected + Received Object { "0": "pipe:[39789]", "1": "pipe:[39790]", "10": "pipe:[39804]", "11": "pipe:[39804]", "114": "pipe:[36857]", "117": "pipe:[36858]", "14": "pipe:[38310]", "15": "pipe:[38310]", "19": "pipe:[37319]", "2": "pipe:[39791]", "20": "pipe:[37319]", "23": "pipe:[38320]", "24": "pipe:[38320]", "27": "pipe:[39808]", "29": "pipe:[39808]", + "32": "/dev/ptmx", "4": "pipe:[38308]", "5": "pipe:[38308]", "6": "pipe:[38309]", "7": "pipe:[38309]", } ❯ onExit tests/index.test.ts:65:34 ❯ wrapper.ts:88:9 ❯ processTicksAndRejections node:internal/process/task_queues:95:5 This error originated in "tests/index.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 "spawns and exits". 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.

AssertionError: expected { '0': 'pipe:[39789]', …(19) } to strictly equal { '0': 'pipe:[39789]', …(18) } - Expected + Received Object { "0": "pipe:[39789]", "1": "pipe:[39790]", "10": "pipe:[39804]", "11": "pipe:[39804]", "114": "pipe:[36857]", "117": "pipe:[36858]", "14": "pipe:[38310]", "15": "pipe:[38310]", "19": "pipe:[37319]", "2": "pipe:[39791]", "20": "pipe:[37319]", "23": "pipe:[38320]", "24": "pipe:[38320]", "27": "pipe:[39808]", "29": "pipe:[39808]", + "32": "/dev/ptmx", "4": "pipe:[38308]", "5": "pipe:[38308]", "6": "pipe:[38309]", "7": "pipe:[38309]", } ❯ onExit tests/index.test.ts:65:34 ❯ wrapper.ts:88:9 ❯ processTicksAndRejections node:internal/process/task_queues:95:5 This error originated in "tests/index.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 "spawns and exits". 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.

AssertionError: expected { '0': 'pipe:[39789]', …(19) } to strictly equal { '0': 'pipe:[39789]', …(18) } - Expected + Received Object { "0": "pipe:[39789]", "1": "pipe:[39790]", "10": "pipe:[39804]", "11": "pipe:[39804]", "114": "pipe:[36857]", "117": "pipe:[36858]", "14": "pipe:[38310]", "15": "pipe:[38310]", "19": "pipe:[37319]", "2": "pipe:[39791]", "20": "pipe:[37319]", "23": "pipe:[38320]", "24": "pipe:[38320]", "27": "pipe:[39808]", "29": "pipe:[39808]", + "32": "/dev/ptmx", "4": "pipe:[38308]", "5": "pipe:[38308]", "6": "pipe:[38309]", "7": "pipe:[38309]", } ❯ onExit tests/index.test.ts:65:34 ❯ wrapper.ts:88:9 ❯ processTicksAndRejections node:internal/process/task_queues:95:5 This error originated in "tests/index.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 "spawns and exits". 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.

AssertionError: expected { '0': 'pipe:[39789]', …(19) } to strictly equal { '0': 'pipe:[39789]', …(18) } - Expected + Received Object { "0": "pipe:[39789]", "1": "pipe:[39790]", "10": "pipe:[39804]", "11": "pipe:[39804]", "114": "pipe:[36857]", "117": "pipe:[36858]", "14": "pipe:[38310]", "15": "pipe:[38310]", "19": "pipe:[37319]", "2": "pipe:[39791]", "20": "pipe:[37319]", "23": "pipe:[38320]", "24": "pipe:[38320]", "27": "pipe:[39808]", "29": "pipe:[39808]", + "32": "/dev/ptmx", "4": "pipe:[38308]", "5": "pipe:[38308]", "6": "pipe:[38309]", "7": "pipe:[38309]", } ❯ onExit tests/index.test.ts:65:34 ❯ wrapper.ts:88:9 ❯ processTicksAndRejections node:internal/process/task_queues:95:5 This error originated in "tests/index.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 "spawns and exits". 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.