-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
CI: run flaky tests on firefox browsers #6411
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
@@ -146,8 +146,7 @@ jobs: | |||
strategy: | |||
matrix: | |||
node-version: [18.18.0] | |||
# Currently using single browser & os combination for flaky tests to reduce cost impact | |||
browser: ['chromium'] | |||
browser: ['chromium', 'firefox'] |
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.
Should we use all browsers ? Not just Firefox
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.
sorry just saw this, the other is webkit, we can see how it goes with adding firefox. just alittle weary there will be alot of flaky jobs (since its 3 per browser)
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 think the workflow anyways run separately for all browsers after isolation, so running 2 or 3 browser will not make a difference, but the objective was to see if flakyness appears in isolation or not and fix it ..
Description
Describe the changes in this pull request
to see if putting flaky test in a less crowded run helps with the flakiness since most of the flaky tests are on firefox
Test plan
wait for CI to run, there should be a FF job for flaky test