From: Eric Wong <normalperson@...>
Date: 2018-09-13T02:00:02+00:00
Subject: [ruby-core:88967] Re: Fwd: [ruby-alerts:9024] failure alert on	trunk@P895 (NG (r64706))

Koichi Sasada <ko1@atdot.net> wrote:
> any idea?

Maybe r64707, except spawn shouldn't call fork there
(only vfork).  Seems similar to [ruby-core:88774] and very rare
to hit.  Any other CI machines hit EINVAL on pthread_mutex_unlock?

I'm 99% sure r64707 fixes A bug, but I don't know if it fixes THIS bug...

Do you have ./configure log output?

> rsult : NG (r64706)
> detail: https://gist.github.com/6a8e880353fc1220cba65d38e247dd7b

>  @logfile="/home/ko1/ruby/logs/brlog.trunk.20180913-100644",

> http://ci.rvm.jp/results/trunk@P895/1313604

I can't find configure output in those.  Thanks.

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