-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: default jest config will sometimes result in shards with 0 tests #13027
Comments
can i work on this issue? |
Here's a replay of the issue, for what it's worth https://app.replay.io/recording/jest-shards-can-sometimes-have-0-tests-in-them--03c102a9-23de-4dff-9703-33c21e3103bc?point=649037107455789718243409532026952&time=1478.2236363636364&hasFrames=true |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
/reopen |
PR welcome!
Super cool 😀 |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
@rahul3002 are you still up for sending a PR? /cc @marionebl FYI |
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. |
Version
28.1.3
Steps to reproduce
git clone git@github.com:jazzdan/jest-shard-bug.git
cd jest-shard-bug
yarn install
yarn reproduce
Expected behavior
I would expect the 12/12 shards to contain at least 1 test, ideally 4. There are 55 tests and 12 shards. I would expect each shard to contain at least 4 tests since 55/12 = 4 and some change.
Actual behavior
Instead the 12th shard contains 0 tests, which is an error by default in jest.
I know I can implement my own test sequencer but it was surprising to me that using the default sequencer with a default jest config and shards could result in an error.
Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: