From: Eric Wong <normalperson@...>
Date: 2018-12-22T08:13:42+00:00
Subject: [ruby-core:90671] Re: [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI

takashikkbn@gmail.com wrote:
> As of r66490, the test on some CIs is still failing for different reasons.
 
> > Expected "#<Process::Status: pid 515 SIGKILL (signal 9)>" to be empty.

OK, I lowered thread counts in r66494.

Btw, can we get dmesg or kernel logs from those CI machines to
confirm it was OOM killer?  I guess RLIMIT_NPROC was a bad check
anyways; and OOM killer is a little unpredictable...

> > ArgumentError: invalid resource name: NPROC

Interesting; I haven't touched Solaris in ages but I never
thought it lacked RLIMIT_NPROC.  So I unconditionally removed
the check.


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