Unhandled Rejection Error during 'Rerun' in Watch Mode after Yarn v3 Installation

[YoshimiShima]

Hi,

Our team recently migrated to Yarn v3, and since then, we've been experiencing an Unhandled Rejection error that seems to be occurring specifically during the 'Rerun' phase of Vitest's watch mode. This error has been consistently causing the watch mode to terminate prematurely.

The error message we receive is as follows:

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Error: file closed
 ❯ FileHandle.[kRef] .pnp.cjs:12276:19
 ❯ FileHandle.writeFile .pnp.cjs:12200:17
 ❯ Object.writeFile .pnp.cjs:12499:39
 ❯ IndentedLogger.baseLog .yarn/__virtual__/vitest-virtual-b14e2e80d9/0/cache/vitest-npm-0.31.2-c317753f5b-a4d721f56c.zip/node_modules/vitest/dist/vendor-cli-api.35332ab3.js:9501:53
 ❯ IndentedLogger.log .yarn/__virtual__/vitest-virtual-b14e2e80d9/0/cache/vitest-npm-0.31.2-c317753f5b-a4d721f56c.zip/node_modules/vitest/dist/vendor-cli-api.35332ab3.js:9373:17
 ❯ JUnitReporter.onFinished .yarn/__virtual__/vitest-virtual-b14e2e80d9/0/cache/vitest-npm-0.31.2-c317753f5b-a4d721f56c.zip/node_modules/vitest/dist/vendor-cli-api.35332ab3.js:9577:23
 ❯ .yarn/__virtual__/vitest-virtual-b14e2e80d9/0/cache/vitest-npm-0.31.2-c317753f5b-a4d721f56c.zip/node_modules/vitest/dist/vendor-cli-api.35332ab3.js:13966:51
 ❯ Vitest.report .yarn/__virtual__/vitest-virtual-b14e2e80d9/0/cache/vitest-npm-0.31.2-c317753f5b-a4d721f56c.zip/node_modules/vitest/dist/vendor-cli-api.35332ab3.js:13964:38
 ❯ .yarn/__virtual__/vitest-virtual-b14e2e80d9/0/cache/vitest-npm-0.31.2-c317753f5b-a4d721f56c.zip/node_modules/vitest/dist/vendor-cli-api.35332ab3.js:13719:18

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: {
  "code": "EBADF",
  "syscall": "writeFile",
}

Could you provide any insight or suggestions on how we might resolve this issue? Any assistance would be greatly appreciated.

Thank you in advance.

[AriPerkkio]

I can reproduce this issue in watch mode when JUnit reported is enabled, even without Yarn.

Looks like I broke this in 9263e25. We'll need to fix this and add a test case to watch mode tests.

Progress can be tracked here: #3496

[YoshimiShima]

Thank you so much! I have confirmed that the bug is fixed! I really appreciate your help!