You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jest normally runs test files in order of how long they took to run last time, with the longest-running first.
jest-runner-eslint doesn't seem to do this. Files are linted in a seemingly random order.
It appears that the runner is not outputting timing information to Jest, or for some reason Jest is not recording it. In Jest's cache folder, for a normal test run, there's a perf-cache file which records timings. e.g.:
Jest normally runs test files in order of how long they took to run last time, with the longest-running first.
jest-runner-eslint
doesn't seem to do this. Files are linted in a seemingly random order.It appears that the runner is not outputting timing information to Jest, or for some reason Jest is not recording it. In Jest's cache folder, for a normal test run, there's a
perf-cache
file which records timings. e.g.:The last number represents the number of milliseconds the test file took to run.
In comparison, the
perf-cache
file created after anjest-runner-eslint
run:Every file has a recorded duration of 0, so Jest cannot sequence the files.
I'd be happy to make a PR if someone can point me in the right direction.
The text was updated successfully, but these errors were encountered: