You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running on rbx 2.0.0dev from today on 64-bit ubuntu 12.04. I'm working on better signal handling in resque here. The tests are failing for me on Travis. I debugged some more locally and made a smaller repro case. In rbx it bails out fairly quickly not really obeying the timings.
$ time PATH=$PATH:/usr/local/rubinius/2.0.0dev/bin /usr/local/bin/rbx/rbx worker.rb
FAILURE
real 0m2.266s
user 0m0.228s
sys 0m0.032s
vs MRI 1.9.3-p194
$ time ruby worker.rb
SUCCESS!
real 0m12.031s
user 0m0.016s
sys 0m0.012s
The text was updated successfully, but these errors were encountered:
What a wonderful MRI behavior we see here again. What MRI does is when a
SignalException escapes to the toplevel, it catches it, sets up the
default signal handler for that signal and reraises the signal to the
current process. We therefore mimic this behavior by setting up signal
handlers for the same signals MRI catches and raises an exception. Our
post handling then does the same by setting up the default handler and
resending the signal.
Fixesrubinius#1839
I'm running on rbx 2.0.0dev from today on 64-bit ubuntu 12.04. I'm working on better signal handling in resque here. The tests are failing for me on Travis. I debugged some more locally and made a smaller repro case. In rbx it bails out fairly quickly not really obeying the timings.
vs MRI 1.9.3-p194
The text was updated successfully, but these errors were encountered: