-
Notifications
You must be signed in to change notification settings - Fork 446
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
Improve test quality by either improving or removing unreliable test #692
Comments
Every PR will pass all tests before merging. There are a lot of questions (e.g. #618 #634 #638) in the existing compatibility tests. Some of them are fixed, e.g. #620 and #621. We still need more time to fix all of them.
This is a good idea. We can discuss this in the next community sync. |
For short term, I think it's better to rerun the tests for merged commits before the compatibility get fixed |
Makes sense! Some other potential actions we considered: |
This actually looks really bad. We don't even know it's flaky tests or test failures.
The text was updated successfully, but these errors were encountered: