Thanks to confirm.

Not sure why, but recent 2 daily builds (r64397, r64417) worked fine.
2018ǯ816() 8:16 Eric Wong <normalperson / yhbt.net>:
>
> Eric Wong <normalperson / yhbt.net> wrote:
> > Takashi Kokubun <takashikkbn / gmail.com> wrote:
> > > The skip commit didn't let the --jit-wait CI succeed anyway. So I'm
> > > searching which commit of yesterday caused the failure. The cause
> > > could be overall slowdown or hanging on one test, but not sure yet
> > > because it's silently finished by timeout.
> >
> > I guess --jit-wait failure is my fault :x   Will investigate
>
> Once in a blue moon, I get this, not sure why, yet:
>
> IMAPTest#test_exception_during_idle:
> Test::Unit::ProxyError: Attempt to unlock a mutex which is locked by another thread
>     /foo/ruby/lib/monitor.rb:200:in `unlock'
>     /foo/ruby/lib/monitor.rb:200:in `mon_exit'
>     /foo/ruby/lib/monitor.rb:228:in `ensure in mon_synchronize'
>     /foo/ruby/lib/monitor.rb:228:in `mon_synchronize'
>     /foo/ruby/lib/net/imap.rb:957:in `idle'
>     /foo/ruby/test/net/imap/test_imap.rb:246:in `test_exception_during_idle'
>
> Finished tests in 29.648353s, 0.0337 tests/s, 0.0000 assertions/s.
> 1 tests, 0 assertions, 1 failures, 1 errors, 0 skips

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