fix: upgrade write-atomic-file to support worker_threads

[SimenB]

Summary

EDIT: We can probably just bump the version instead, hopefully the PR will land really quick 🙂 npm/write-file-atomic#37 (comment)

Due to worker_threads sharing process.pid with its parent, write-file-atomic doesn't really work when run inside a worker. See this example (using jest-worker@24.0.0-alpha.12):

// worker.js
const {default: Worker} = require('jest-worker');

const w = new Worker(require.resolve('./file'));

w.getStdout().pipe(process.stdout);
w.getStderr().pipe(process.stderr);

console.log('parent pid', process.pid);

Promise.all([w.hello(), w.hello(), w.hello(), w.hello(), w.hello()])
  .catch(e => {
    console.error(e);
  })
  .then(() => w.end());

// file.js
module.exports.hello = () => console.log('child pid', process.pid);

$ node -v
v10.14.1
$ node worker
parent pid 82720
child pid 82721
child pid 82721
child pid 82721
child pid 82722
child pid 82723
$ node --experimental-worker worker
parent pid 82778
child pid 82778
child pid 82778
child pid 82778
child pid 82778
child pid 82778

With this fork, we use worker_threads.threadId instead of process.pid.

To test, navigate to e2e/coverage-report and run ../../jest --coverage --coverageThreshold '{"global": {"lines": 100}}' --collectCoverageOnlyFrom cached-duplicates/a/identical.js --collectCoverageOnlyFrom cached-duplicates/b/identical.js -- identical.test.js --no-cache

Without this change, it crashes every time due to being unable to write the cache file. With these changes, it passes

Opened up PR: npm/write-file-atomic#37

Test plan

Green CI on node 11 (or at last fixed coverage tests) 🤞

[SimenB]

The fix has been merged and released upstream(:tada:), so I've changed this PR to just update the dep.

I verified that the reproduction from the OP now passes. This will still fail CI, however (see #7681)

[iarna]

I just released a patch release with a fix for a signal-exit leak, so you may want to bump again to 2.4.1!

[SimenB]

Thanks for the heads-up! 0e1855e

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.