-
Notifications
You must be signed in to change notification settings - Fork 18.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
Epic: Fix Flaky tests #19480
Comments
ping @vdemeester, our master of tests! 🐸 |
@thaJeztah I submitted a PR: #19653 |
@thaJeztah, I just saw TestRunSeccompAllowAptKey fail, and I feel like I've seen other tests fail with similar (or identical) output:
Does that look familiar to you? |
@clnperez I think that's because the key server is down. Unfortunately we've seen that happening regularly, so we may need to think of using other key servers, or whatever. |
Gonna close this one as the original list is fixed and we track the other individually for now 👼 |
Fix Flaky tests
There's a number of tests that are intermittently failing. Given that a whole
test run can take up to three hours on ARM, these tests are giving us serious
headaches.
There's a list of tests that are known to be flaky.
If you discover additional tests that are possibly flaky; open a new issue,
and use
Flaky test:
in the title. Also ping a maintainer to have the"flaky test" label added and have it added to the list below.
Test duration
There's also a related issue for reducing the total duration of our tests;
Optimize slow bottleneck tests
that we could use some help on.
If you want to work solving one of these tests, leave a comment, and we add
your name to the list below!
PR Flaky test: Test Docker daemon ungracefully restart #19653 (@wenchma)not fully resolved (gccgo failing)PR Fix flaky test, TestDockerNetworkHostModeUngracefulDaemonRestart #20246TestGetContainerStatsRmRunning
#19570The text was updated successfully, but these errors were encountered: