-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[*] Chore: Mark additional tests as flaky from #6535 test runs #6536
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
The plain text tests are expected to fail until #6535 is merged and this is updated |
the criteria to mark flaky (decided with @Sahejkm ) was if a test failed on a PR due to flakiness. however also ok to adjust the criteria to occasionally include non failing tests with flaky runs, since it was a bother |
Every test that has a flaky run has a chance of failing, it's just probability. The more we have the more often it's going to be a problem. |
Description
We still have a lot of tests that are flaky, which is a considerable burden on contributions and reviewing them. This is just the ones that flaked in #6535 on this particular run https://github.com/facebook/lexical/actions/runs/10481362302/job/29033662935
Test plan
Before
After
These 9 tests are tagged
@flaky