jest: Jest fails with EBADF: bad file descriptor, close

I can confirm 23.6.0 is affected too and was fixed by using npm resolutions

and

  "resolutions": {
    "write-file-atomic": "2.4.1"
  }

in package.json

this was happening with jest 23.6 for my team as well. I went ahead and added "write-file-atomic": "2.4.1" to resolutions in my package.json: "resolutions": { "write-file-atomic": "2.4.1" },

24.1.0 is out: https://github.com/facebook/jest/commit/8a2ea1e83845497fa7756b44c91f6ff97eb02692

Feels a bit dirty using resolutions… do we know when a 24.0.1 or 24.1 will be out?

That’s an issue either with your network or a proxy/registry of some kind. It’s definitely available:

https://www.npmjs.com/package/jest

Could the fix be also applied to 23.x versions?

No, not unless absolutely necessary. And we have don’t really have a fix. The “fix” is to rollback write-file-atomic, which you can do yourself with a lockfile or yarn’s resolutions. 2.4.2 is the one with the error, so use 2.3.0 (what jest 23 came with) or 2.4.0/2.4.1

Same problem once upgrading to jest 24, windows 10. I’ve downgraded write-file-atomic to 2.4.1 with manual copying of an old version and it stopped having errors. re installing and the error comes back. i cleared my cache before each test.

Related to #4444 (last few comments there), seems like something in the upgrade from write-file-atomic 2.3.0 -> 2.4.2 broke something.

Can you try to either manually edit node_modules/write-file-atomic/index.js or use yarn resolutions to force 2.3.0 and see if that fixes your error?

Diff: https://github.com/npm/write-file-atomic/compare/v2.3.0...v2.4.2

I encountered this problem today on our large scale project. We use locked 23.6.0 jest version. Could the fix be also applied to 23.x versions?

I’m also seeing this error after upgrading. Was previously using jest@23.6 successfully. Post upgrade getting this cache error randomly.

Oh, and btw, if you use Yarn, feel free to use the "resolutions" field in package.json to get this done, or use the patch-package project 🙂

I encountered this problem today on our large scale project. We use locked 23.6.0 jest version. Could the fix be also applied to 23.x versions?

22.4 also has this issue

That’s great, just letting the next google-fu-master that finds this thread to avoid trying the workaround if they might be using yarn workspaces.

I’ve opened up #7725. @pribilinskiy it would be awesome if you could test by installing write-file-atomic@2.4.1 (jest comes with 2.4.2) locally and see if it fixes your issue. Either uses resolutions if you use yarn, or manually replacing in node_modules

Plain jest.

abbreviated jest.config.js

{
	automock: true,
	cacheDirectory: '<rootDir>/.jest-cache',
	clearMocks: true,
	collectCoverageFrom: [...],
	coverageReporters: ['text-summary', 'html', 'clover'],
	coverageThreshold: {
		global: {
			statements: 85,
			branches: 80,
			functions: 72,
			lines: 85,
		},
	},
	moduleFileExtensions: ['tsx', 'ts', 'js', 'json'],
	moduleNameMapper: {
		'cv/(.*)': '<rootDir>/node_modules/content-viewer/dist/commonjs/$1',
	},
	setupTestFrameworkScriptFile: '<rootDir>/jestEnvironment.js',
	testEnvironment: 'node',
	testPathIgnorePatterns: ['_Auth', 'IntegrationSpec'],
	testRegex: 'Spec.tsx?$',
	timers: 'fake',
	transform: {
		'\\.(ts|tsx)$': '<rootDir>/src/testHelpers/transformTS.js',
		'\\.(css|svg|gif|png|jpg|jpeg)$': '<rootDir>/src/testHelpers/transformResource.js',
	},
	unmockedModulePathPatterns: [...],
}