multirunner with a wrong project path will try to run tests incorrectly

[aaronabramov]

having

// config.js
module.exports = {
  projects: [
    'non_existing_path/',
    'another_non_existing_path/',
  ],
};

and running

jest --config config.js

will not throw, but try to run jest with some incorrect configuration, which makes it very frustrating to debug.

also

jest --config config.js --showConfig

will not print the accurate config (it'll only print one projectConfig and one globalConfig)

[gaearon]

Just spent an hour here 😄

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