Maybe those tests should be fixed instead?
It seems a bug if a test creates 1000+ threads to the point
pthread_create() fails, except if that test is specifically testing
for that condition.

On Wed, Jul 4, 2018 at 5:13 AM, Eric Wong <normalperson / yhbt.net> wrote:
>> test_all             <main>: warning: pthread_create failed for timer: Resource temporarily unavailable, scheduling broken
>> <main>: warning: timer thread stack size: 16384
>
> Many CI failures are caused by pthread_create failing for timer.
>
> I will try using POSIX timers API (timer_create/timer_settime/...)
> on such platforms to eliminate timer thread (at least for
> single-threaded code).  I'll keep old timer-thread coded path
> to make cross-platform testing easier, however.
>
> It will take into consideration waitpid+SIGCHLD along with
> "Timeout in VM" <https://bugs.ruby-lang.org/issues/14859>
>
> Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

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