Multi-project runner can't find some mocks

[gaearon]

Do you want to request a feature or report a bug?

Bug.

What is the current behavior?

In some cases (can't determine when) Jest "loses" some mocks with multi-project runner and emits weird messages.

You can reproduce by cloning facebook/react#10273 and running npm test. Many failures are expected but these (about missing files) are not.

What is the expected behavior?

Jest can find mocked modules when running with multi-project runner.

Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.

Please use facebook/react#10273 as a base.

[cpojer]

@aaronabramov I believe the reason for this one is that the two configs live in the same folder (or run in the same rootDir) and don't have a name field in the config, which means we'll use rootDir for the cacheKey, which then results in the two projects writing and using the same cache. Should be easy to validate by adding a name field to the two config files.

[SimenB]

If the above hypothesis is correct, this has been fixed by #5862

[github-actions]

This issue 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.