@vue/cli-plugin-unit-jest fails with error EBADF: bad file descriptor, close

[phil-scott-78]

Version

3.5.0

Reproduction link

https://github.com/phil-scott-78/jest-EBADF

Environment info

Windows 10

Steps to reproduce

npm run unit:test

What is expected?

Tests to run

What is actually happening?

Sporadic failure with an error EBADF: bad file descriptor

---

This is due to write-file-atomic@2.4.2. Newer versions of jest have been updated to force the version to 2.4.1.

See:

• Jest fails with EBADF: bad file descriptor, close jestjs/jest#7709
• Jest run fails with EBADF: bad file descriptor npm/write-file-atomic#39

[haoqunjiang]

Actually I can't reproduce this issue locally. But according to the discussions in the above link, it may be related to race conditions across multiple processes, so you can try to enable --runInBand flag to see if the error disappears:

npm run test:unit -- --runInBand

[phil-scott-78]

Thanks for your quick reply. Ran it with --runInBand a few times and it does seem to resolve it. Also seemed to have success with a specific resolution when using yarn. But I don't really want to update build scripts and the such with this work around. Fortunately I can hold off on the upgrade on vue-cli for a while until a new version of @vue/cli-plugin-unit-jest is pushed with the latest version of jest.