From: Eric Wong <normalperson@...>
Date: 2018-08-18T09:20:43+00:00
Subject: [ruby-core:88539] Re: [Ruby trunk Feature#15002] [PATCH] thread.c (sleep_*): reduce the effect of spurious interrupts

takashikkbn@gmail.com wrote:
> Thanks to deal with it. Actually test-all with --jit-wait is
> running successfully on my Wercker CI and ko1's
> trunk-mjit-wait for now
> http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker, but
> as long as it passes the tests on your environment, it looks
> good to merge the change to deal with the spurious interrupts
> by SIGCHLD from MJIT.

OK, r64444 is committed.  It should fix spurious wakeups from
the new ConditionVariable#wait specs

> > TestThreadQueue#test_queue_close_multi_multi [/ruby/test/ruby/test_thread_queue.rb:526]:
> > no threads running

> > TestIO#test_recycled_fd_close [/ruby/test/ruby/test_io.rb:3804]:
> > Expected /stream closed/ to match "closed stream".

So you guys don't see these two failures under CI?
I got them every time...

> >   3) Failure:
> > TestRubyOptimization#test_tailcall_condition_block [/ruby/test/ruby/test_optimization.rb:439]:
> > [ruby-core:78015] [Bug #12905]: 10079 / 20158 stack levels.
> > Exception raised:
> > <#<SystemStackError: stack level too deep>>.

This one might be sporadic, I don't think I saw it every time.

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>