ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:90895] Re: [ruby-alerts:11680] failure alert on trunk-mjit@silicon-docker (NG (r66707))
Date: Sat, 5 Jan 2019 09:27:59 +0000	[thread overview]
Message-ID: <20190105092759.hgf524iedwaidw7n@dcvr> (raw)
In-Reply-To: <20190104115414.CE64B3BED45@mail.atdot.net>

ko1c-failure@atdot.net wrote:
> detail: https://gist.github.com/1a4b78d8a2f95141391e5276210e65e9

> :   1)
> : TestIO#test_read_nonblock_no_exceptions [/tmp/ruby/src/trunk-mjit/test/ruby/test_io.rb:1508]:
> : <nil> expected but was
> test-spec: 3712 files, 30218 examples, 103102 expectations, 0 failures, 0 errors, 0 tagged

> http://ci.rvm.jp/results/trunk-mjit@silicon-docker/1595151

This is not a new issue, [ruby-alerts:9827] (2018-10-29)
https://gist.github.com/3a0e38dd7fc39a290d1ffff607b56f8d
http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/1435275

I suspect there is another thread which forks and holds keeps
the pipe open so it gives EAGAIN instead of EOF.

       reply	other threads:[~2019-01-05  9:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190104115414.CE64B3BED45@mail.atdot.net>
2019-01-05  9:27 ` Eric Wong [this message]
2019-01-05 12:38   ` [ruby-core:90896] Re: [ruby-alerts:11680] failure alert on trunk-mjit@silicon-docker (NG (r66707)) Takashi Kokubun
2019-01-05 20:04     ` [ruby-core:90902] " Eric Wong
2019-01-06  0:58       ` [ruby-core:90908] " Takashi Kokubun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190105092759.hgf524iedwaidw7n@dcvr \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).