-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
test: Run playwright tests in parallel #7334
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
Conversation
size-limit report 📦
|
82a097e
to
379f59e
Compare
// Run tests inside of a single file in parallel | ||
fullyParallel: true, | ||
// Use 3 workers on CI, else use defaults (based on available CPU cores) | ||
workers: process.env.CI ? 5 : undefined, |
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.
l: Any reason for 5 specifically?
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.
No, it was 3 previously and I randomly set it to 5 to see if it still works as expected, and it did (and was slightly faster on CI). FYI without this on CI it defaults to just one worker, because CI has two cores, and the default heuristic is # of CPUS/2
.
I can also leave it at 3 for CI (but I guess that is equally random 😅 )
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.
No 5 is totally fine, I was just wondering 😅
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.
I will adjust the comment to make it clear this is an arbitrary number! 😂
This:
workers
config for playwright, making sure we use the default on local machines (which depends on available CPU cores), and bump it to 5 on CI to speed this up slightly