From: Eric Wong <normalperson@...>
Date: 2018-10-29T15:22:24+00:00
Subject: [ruby-core:89619] Re: [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process

takashikkbn@gmail.com wrote:
> > Ah, so the waitpid from #system is on /bin/rm (I missed that earlier) 
> 
> For http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/1431394, yes. Others http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/1431775 http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/1430875 are on waitpid for different things.

OK, first patch for #system is here:

   https://80x24.org/spew/20181029151106.9474-1-e@80x24.org/raw

It took me a few iterations because of error handling, so I
shoved the lock as deep into where fork/vfork is actually called
to avoid deadlocks and stalls on FIFOs.

I plan to build on this for MJIT...

Greg: everything should be confined to *nix for now, but can you
make sure I didn't break anything on Windows?  Thanks.

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