-
Notifications
You must be signed in to change notification settings - Fork 589
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
[e2e] Brody/e2e parallel #5786
[e2e] Brody/e2e parallel #5786
Conversation
"detox:ios:tests": "detox test -c ios.sim.debug --maxWorkers 2 -- --bail 1", | ||
"detox:ios": "detox build -c ios.sim.debug | xcpretty --color && yarn detox:ios:tests", | ||
"detox:ios:release": "detox build -c ios.sim.release && detox test -c ios.sim.release --maxWorkers 2 -- --bail 1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens when maxWorkers > 2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
more parallelization, but diminishing returns obvs. we have 6 tests RIGHT NOW with more to come.
1 worker = 16 mins
2 workers = 8 mins
3 workers = 5.33 mins
right now 4+ workers is awkward bc the tests become uneven so it caps out at 5.33 minutes until we hit 6 workers (num of tests).
once we add more workers and split up the tests more i think the flakiness could become a concern bc of how split resources become. i'll see how far i can push it tho! i think at least 3 is probably good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah i tried it out it seemed like more than 2 workers currently introduces some flakiness
What changed (plus any additional context for devs)