Fix chmod error when different owner's dir exists in preprocess-cache

[yudoufu]

If /tmp/jest_preprocess_cache already exists by different owner then preprocess-cache raises chmodSync permission error.

e.g. When many users run Jest on a shared-server, raise following error:

Error: /<snip>/node_modules/babel-jest: EPERM, operation not permitted '/tmp/jest_preprocess_cache'
  at Object.fs.chmodSync (fs.js:833:18)
  at Object.readAndPreprocessFileContent (/<snip>/node_modules/jest-cli/src/lib/utils.js:392:12)
  at Loader._execModule (/<snip>/node_modules/jest-cli/src/HasteModuleLoader/HasteModuleLoader.js:209:11)
  at Loader.requireModule (/<snip>/node_modules/jest-cli/src/HasteModuleLoader/HasteModuleLoader.js:914:12)
  at jasmineTestRunner (/<snip>/node_modules/jest-cli/src/jasmineTestRunner/jasmineTestRunner.js:292:16)
  at /<snip>/node_modules/jest-cli/src/TestRunner.js:376:12
  at tryCatcher (/<snip>/node_modules/jest-cli/node_modules/bluebird/js/main/util.js:26:23)
  at Promise._settlePromiseFromHandler (/<snip>/node_modules/jest-cli/node_modules/bluebird/js/main/promise.js:503:31)
  at Promise._settlePromiseAt (/<snip>/node_modules/jest-cli/node_modules/bluebird/js/main/promise.js:577:18)
  at Promise._settlePromises (/<snip>/node_modules/jest-cli/node_modules/bluebird/js/main/promise.js:693:14)
  at Async._drainQueue (/<snip>/node_modules/jest-cli/node_modules/bluebird/js/main/async.js:123:16)
  at Async._drainQueues (/<snip>/node_modules/jest-cli/node_modules/bluebird/js/main/async.js:133:10)
  at Async.drainQueues (/<snip>/node_modules/jest-cli/node_modules/bluebird/js/main/async.js:15:14)
  at process._tickCallback (node.js:448:13)

So, I fixed it.

[cpojer]

Thank You!

[jsdf]

This change shouldn't have removed the handling for the EEXIST error. There is a race condition which now occurs when the preprocess cache dir is created by another process in between the fs.existsSync check and the fs.mkdirSync, which is quite likely seeing as all the workers are trying to create it at the same time.

[jsdf]

The issue experienced by @yudoufu would be fixed by the combination of the preprocess cache dir respecting the cache dir config (#470) and ensuring that the configured cache dir is somewhere that the user has the correct permissions for.

[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.