-
Notifications
You must be signed in to change notification settings - Fork 43
The first two tests are blocking for over 60 seconds in Travis (using assert_cmd) #43
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
Comments
You are having the opposite problem of me with #4. Your tests build with This is a tricky situation. Ideally, we'd always pass along Options
|
btw once this is confirmed to be the problem, I'd like to merge these notes into #4. |
Yes, this is the problem. Testing with
I'm not quite understand the tricky situation, and how it affects the Anyway, for the solution, I prefer to a esay/intuitive one like a feature flag to opt-in. |
Closing in favor of #4 |
As described mesalock-linux/mesabox#41. I don't know why the first tests are always blocking for over 60 seconds. However, after the blocking issue, all testcases can be run without any problem.
This only happens in Travis: https://travis-ci.org/mesalock-linux/mesabox/jobs/411140601#L1305
I cannot reproduce this issue in my machine. Don't know why.
The text was updated successfully, but these errors were encountered: