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.

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

Closed
12 tasks done
thaJeztah opened this issue Jan 20, 2016 · 6 comments
Closed
12 tasks done

Epic: Fix Flaky tests #19480

thaJeztah opened this issue Jan 20, 2016 · 6 comments

Comments

@thaJeztah
Copy link
Member

thaJeztah commented Jan 20, 2016

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!

@thaJeztah thaJeztah added the priority/P1 Important: P1 issues are a top priority and a must-have for the next release. label Jan 20, 2016
@thaJeztah
Copy link
Member Author

ping @vdemeester, our master of tests! 🐸

@WeiZhang555
Copy link
Contributor

Already pushed a fix for #18679, PR: #19570

@wenchma
Copy link
Contributor

wenchma commented Jan 25, 2016

@thaJeztah I submitted a PR: #19653
fix TestDockerNetworkHostModeUngracefulDaemonRestart (on experimental) #19368

@clnperez
Copy link
Contributor

clnperez commented Feb 4, 2016

@thaJeztah, I just saw TestRunSeccompAllowAptKey fail, and I feel like I've seen other tests fail with similar (or identical) output:

20:40:48 gpg: requesting key F6B0FC61 from hkp server p80.pool.sks-keyservers.net
20:40:48 gpgkeys: key E871F18B51E0147C77796AC81196BA81F6B0FC61 can't be retrieved
20:40:48 gpg: no valid OpenPGP data found.
20:40:48 gpg: Total number processed: 0
20:40:48 : exit status 2

Does that look familiar to you?

@thaJeztah
Copy link
Member Author

@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.

@icecrime icecrime removed the priority/P1 Important: P1 issues are a top priority and a must-have for the next release. label Jul 27, 2016
@vdemeester
Copy link
Member

Gonna close this one as the original list is fixed and we track the other individually for now 👼

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants