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

Travis devicemapper-rs tests failing regularly with EBUSY #557

Closed
jbaublitz opened this issue Jun 23, 2020 · 4 comments
Closed

Travis devicemapper-rs tests failing regularly with EBUSY #557

jbaublitz opened this issue Jun 23, 2020 · 4 comments
Assignees

Comments

@jbaublitz
Copy link
Member

@mulkieran Travis tests were failing for @waltdisgrace pretty regularly with EBUSY on different loopback device tests every time. We seem to have gotten #556 to pass by rerunning it enough times but we should potentially look into what's going on here. I don't think this has anything to do with the code changes, so we may have to think about how we're testing in devicemapper-rs.

@mulkieran
Copy link
Member

Yep, I think this was always a bit of a problem, and I think it's just been happening more and more often. We will have to find a better way, maybe the delay and wait for a particular thing to be true technique will work here, too.

@mulkieran
Copy link
Member

We need to start taking this seriously, it is such a pain.

@mulkieran
Copy link
Member

Pushing to September in hopes that #568 will keep the problem from being annoying for a while.

@mulkieran
Copy link
Member

yeah, that sure worked. Let's not bother to think about it unless it starts bothering us again.

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

2 participants