Skip to content

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

Open
owens-ben opened this issue Dec 11, 2024 · 7 comments · Fixed by #156 or #157
Open

Parallel executions causes suites to be incorrectly created #155

owens-ben opened this issue Dec 11, 2024 · 7 comments · Fixed by #156 or #157

Comments

@owens-ben
Copy link

agent-js-jest v5.1.1, detox 20.26.2

When running parallel executions

For example

image

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.

@owens-ben
Copy link
Author

Anyone taken a look at this?

Generally, when would parallel executions be supported? They worked fine before.

@AmsterGet
Copy link
Member

Hello @owens-ben !

Try the latest version 5.1.2, which is supposed to fix the mentioned suites issues.
Please let me know if everything now works as expected.
I look forward to your feedback!

This was linked to pull requests Jan 30, 2025
@owens-ben
Copy link
Author

@AmsterGet Thanks, just saw this. Will test it out soon and report back.

@AmsterGet
Copy link
Member

@AmsterGet Thanks, just saw this. Will test it out soon and report back.

Hello @owens-ben !
Do you still experience the issue with the mentioned version?

@AmsterGet
Copy link
Member

Hello @owens-ben !

Please take a look at v5.1.3 with few more fixes related to temp ids processing.

@AmsterGet
Copy link
Member

Hello @owens-ben
Have you been able to test mentioned version?
Looking forward to your feedback!

@owens-ben
Copy link
Author

@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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants