-
Notifications
You must be signed in to change notification settings - Fork 38
Parallel executions causes suites to be incorrectly created #155
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
Comments
Anyone taken a look at this? Generally, when would parallel executions be supported? They worked fine before. |
Hello @owens-ben ! Try the latest version 5.1.2, which is supposed to fix the mentioned suites issues. |
@AmsterGet Thanks, just saw this. Will test it out soon and report back. |
Hello @owens-ben ! |
Hello @owens-ben ! Please take a look at v5.1.3 with few more fixes related to temp ids processing. |
Hello @owens-ben |
@AmsterGet Tried 5.1.3 and haven't been able to reproduce the issue with 3, 4, 5+ workers Very much appreciate your help. Cheers! |
agent-js-jest v5.1.1, detox 20.26.2
When running parallel executions
For example
Frequently, a single test will cause a new suite to be created.
I've spent hours debugging that and it just seems to boil down to the fact that the tempId's are not-thread safe.
There was an issue with the previous version 5.0.6 with DB locks that was solved, but now this issue is introduced in 5.1.1, so I'm stuck between 2 broken versions.
The text was updated successfully, but these errors were encountered: