-
Notifications
You must be signed in to change notification settings - Fork 322
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
Revert to IO.select for PerOperation timeouts (fixes #298) #322
Conversation
This kind of sucks as these are specifically the timeouts I feel this optimization would be beneficial for. Nevertheless, it seems prior to Ruby 2.3, we're hitting some kind of MRI bug? /cc @zanker |
Lol Ruby 😔 I fee like we just need something for Travis that has very detailed test semantics for each set of timeout code in each Ruby version. Sent from my iPhone
|
(Looks good) Sent from my iPhone
|
Would be nice if the particular repro case could be turned into some sort of test. That said, timeout tests are the bane of my existence, especially on CI. All that said... on master (Ruby 2.2.4 / OS X 10.11.3):
On this branch:
|
Revert to IO.select for PerOperation timeouts (fixes #298)
I have tried the repro case from #298 from this and this appears to
fix the problem.
Not sure why: the intended semantics appear to be equivalent. Possibly
a MRI bug that was fixed in 2.3?