Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Tracking] High-impact flaky test issues #6774

Open
gjoseph92 opened this issue Jul 20, 2022 · 0 comments
Open

[Tracking] High-impact flaky test issues #6774

gjoseph92 opened this issue Jul 20, 2022 · 0 comments
Labels
flaky test Intermittent failures on CI.

Comments

@gjoseph92
Copy link
Collaborator

gjoseph92 commented Jul 20, 2022 •
edited
Loading

We have lots of flaky tests. But in a lot of cases, many different tests are all failing in the same way. Here are "high impact" classes of CI failures:

  1. 13 different tests: Flaky tests: OSError: Timed out trying to connect to tcp://127.0.0.1:8786 after 5 s #6731, likely includes Flaky tests: plain TimeoutError during client connection to scheduler #6757 for 2 more
  2. 6 different tests: Flaky tests: coroutine 'InProc.write' was never awaited #6551
  3. 2 tests: Flaky tests: ResourceWarning: unclosed cluster SSHCluster #6771
  4. 2 at least: Flaky tests: assert False, (bad_thread, call_stacks) - Worker executor thread still running after Nanny.kill #6796
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
flaky test Intermittent failures on CI.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gjoseph92