[ruby-core:87814] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process

Issue #14867 has been updated by MSP-Greg (Greg L).


@normalperson

Thanks for the patch, I added it, and a build with r63859 locked/froze on test-all.  I’m going to see if I can get any more info by building/testing locally.  I’m surprised and wondering if something reverted wasn’t re-applied, as ruby-loco should be completing test-all with MJIT tests failing…

One question – would the config portion of a ruby-loco build be helpful for you to see?  I can attach it as a text file…


Some more Windows background:

The ruby/ruby repo on GitHub runs two CI builds.  Travis builds on Unbuntu, and Appveyor builds on Windows.

The Appveyor build is what I refer to as mswin.  If both Travis & Appveyor pass, then the ruby/ruby mirror on GitHub shows a green pass flag for each commit.  When either or both fail, people have to look further  to see what the cause of the failure was.

The Appveyor mswin build’s history is shown at https://ci.appveyor.com/project/ruby/ruby/history.

RubyCI.org shows has many builds reported on, and the link to http://mswinci.japaneast.cloudapp.azure.com/vc12-x64/ruby-trunk/recent.html is one of them.  Generally, if mswin passes, so should this build.

So, mswin is used by committers to check whether the Widows VC build succeeded.

Ruby-loco is built using the same build system (MSYS2/MinGW) that the majority of Windows Ruby releases use.  These releases/builds are available for download, as many (new) Windows users/coders are unfamiliar with building/compiling.

Many gems/repos test on Appveyor using the same builds, and many of those also test against trunk.

Some use ruby-loco for that, as I believe it is the only trunk build available with full testing.  The way I have the build script set up, the ‘trunk download’ used for CI testing will always be the most recent passing build. Because of that, I have an interest in making sure it continues to build and pass all tests.

Thanks again, Greg

----------------------------------------
Bug #14867: Process.wait can wait for MJIT compiler process
https://bugs.ruby-lang.org/issues/14867#change-72832

* Author: k0kubun (Takashi Kokubun)
* Status: Assigned
* Priority: Normal
* Assignee: normalperson (Eric Wong)
* Target version: 
* ruby -v: 
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
If Ruby tries to wait for any child process, MJIT's gcc/clang process could be caught by the method call. It's not convenient for both Ruby's user and MJIT worker thread, so Process.wait and its families should somehow avoid waiting for it.

---Files--------------------------------
0001-hijack-SIGCHLD-handler-for-internal-use.patch (13.8 KB)
JIT-test-all.log (39.9 KB)
mjit_test-all_63796.log (40.4 KB)


-- 
https://bugs.ruby-lang.org/

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