-
Notifications
You must be signed in to change notification settings - Fork 28
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
flaky tests #23
Comments
I haven't seen flaky tests for several months so going to close this. If they come back, I've wondered about detecting them with infrequent use of |
Flaky tests have re-appeared, I'm going to re-open this ticket. |
If you observe flaky tests, please add them as a comment on this issue. |
Github actions tool for finding flaky tests, may be worth a look: https://github.com/ctrf-io/github-actions-test-reporter-ctrf |
pytest plugin for generating CTRF report for the above https://pypi.org/project/pytest-json-ctrf/ Do we want a table of all runs or just of runs on main/after PRs are merged? |
I think all runs, why not? |
Identifying flaky tests vs. tests that were temporarily broken by unfinished PRs? |
@callumforrester I've enabled on this draft PR (scroll down to summary section): it hasn't marked any tests as flaky yet, and doesn't provide any easier method of seeing what's flaky/broken. @coretl for comment too https://github.com/bluesky/ophyd-async/actions/runs/10809455998?pr=567 |
Tango tests are apparently flaky because of Tango test infrastructure and there is nothing we can do to fix that. I suggest we report test failures on this ticket and make PRs that The first PR that does this needs to add |
Sometimes CI tests fail. Flaky tests are bad and we should aim to not have any. Here is an example of such a test failing on one instance, but passing when rerun:
https://github.com/bluesky/ophyd-async/actions/runs/10741400139/job/29791703029
FAILED tests/epics/adsimdetector/test_sim.py::test_detector_writes_to_file - bluesky.utils.FailedStatus: <AsyncStatus, task: <coroutine object StandardDetector.trigger at 0x7fecaa70fe60>, errored: TimeoutError()>
The text was updated successfully, but these errors were encountered: