-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
flakey rust test? #777
Comments
probably. introduced in 71370ac. @seanmonstar, do you mind taking a look into this? |
IIRC this test was "fixed" once already in 7f54b52...evidentially there's more going on here. |
I've been looking at this, and so far cannot determine why this error is happening. I don't know if it's flakiness in the test, but I'm a little worried that it's actually flakiness in our TCP proxy... 😢 The logs here, combined with my commentary on how the code works, shows this:
The read of 0 bytes in (3) worries me. That means the proxy closed (or Reproducing this is not easy, so trying to capture some logs is 💀 . |
Just hit this again in CI...
perhaps the CI networking stack is... very unreliable? |
similar but different
|
|
Just saw test output:
|
Just saw a failure of test output:
|
I have been pondering setting our Rust test concurrency to 1... The suite would take slightly longer to complete, but we don't have that many tests... |
Closing due to inactivity. |
master ci failing with
tcp_waits_for_proxies_to_close
, from https://travis-ci.org/runconduit/conduit/jobs/367436260#L1:The text was updated successfully, but these errors were encountered: