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

Flaky test: TestManagerLockUnlock #2182

Closed
aaronlehmann opened this issue May 12, 2017 · 7 comments
Closed

Flaky test: TestManagerLockUnlock #2182

aaronlehmann opened this issue May 12, 2017 · 7 comments

Comments

@aaronlehmann
Copy link
Collaborator

https://circleci.com/gh/docker/swarmkit/7215

--- FAIL: TestManagerLockUnlock (0.22s)
	Error Trace:	manager_test.go:404
	Error:		Should be false

cc @cyli

@cyli
Copy link
Contributor

cyli commented May 12, 2017

Huh, the:

time="2017-05-12T23:11:32Z" level=error msg="failed to re-encrypt TLS key with a new KEK" error="rename /tmp/swarm-ca-test-812740986/.tmp-swarm-node.key604794867 /tmp/swarm-ca-test-812740986/swarm-node.key: no such file or directory" node.id=ygqdkaoi7pnbmkcpat8gmvovi node.role=swarm-manager 
time="2017-05-12T23:11:32Z" level=error msg="failed to re-encrypt TLS key with a new KEK" error="open /tmp/swarm-ca-test-812740986/swarm-node.key: no such file or directory" node.id=ygqdkaoi7pnbmkcpat8gmvovi node.role=swarm-manager 
time="2017-05-12T23:11:32Z" level=error msg="failed to re-encrypt TLS key with a new KEK" error="open /tmp/swarm-ca-test-812740986/swarm-node.key: no such file or directory" node.id=ygqdkaoi7pnbmkcpat8gmvovi node.role=swarm-manager 

right after the test is weird too

@Syntaxide
Copy link
Contributor

@aaronlehmann How often do you see this failure? There doesn't seem to be a good way to search for this on circleci.

@aaronlehmann
Copy link
Collaborator Author

I don't recall seeing this since the original report.

@cyli
Copy link
Contributor

cyli commented Jun 16, 2017

I haven't seen this in a while, and I haven't been able to replicate it easily (I've been running the test over and over in a container somewhere, and can continue to do so until it triggers, but it hasn't yet)

@cyli
Copy link
Contributor

cyli commented Jul 6, 2017

Just as a note, this may have been due to #2281, although it'd be good to try to replicate this still. My attempt to replicate crashed. :P So trying again

@Syntaxide
Copy link
Contributor

I ran this test repeatedly on my laptop for over a week, and found that it ran roughly 10k times without failing. If this test is indeed flaky, it will be more productive to try to isolate the cause of the failure, rather than hoping to catch the flake naturally.

@cyli
Copy link
Contributor

cyli commented Jun 7, 2018

I think this was fixed by #2575.

@cyli cyli closed this as completed Jun 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants