ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: jaruga@redhat.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:99305] [Ruby master Bug#16921] s390x: random test failures for timeout or segmentation fault
Date: Thu, 23 Jul 2020 19:28:30 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-86694.20200723192830.11018@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16921.20200529120644.11018@ruby-lang.org

Issue #16921 has been updated by jaruga (Jun Aruga).


I sent this PR related to this ticket.
https://github.com/ruby/ruby/pull/3354

It's to apply test-scale to test_nogvl_poll.
Other tests I showed above is applying time-scale.

I ran the Ruby tests with `RUBY_TEST_TIMEOUT_SCALE=100 make check` 5 times on Fedora build system s390x . And all ok.
So, I am okay to close this ticket.



----------------------------------------
Bug #16921: s390x: random test failures for timeout or segmentation fault
https://bugs.ruby-lang.org/issues/16921#change-86694

* Author: jaruga (Jun Aruga)
* Status: Open
* Priority: Normal
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
I observed the following error related to timeout or segmentation fault on Ruby 2.7.1 s390x in Fedora builds. The tests somtimes fail. It seems the s390x machine used in CI is slow. It's great if we can change the timeout casually if it essentially comes from the length of the timeout.

It might be related to #16492 .


```
  1) Failure:
Fiddle::TestFunction#test_nogvl_poll [/builddir/build/BUILD/ruby-2.7.1/test/fiddle/test_function.rb:95]:
slept amount of time.
Expected |200 - 714| (514) to be <= 180.
```

```
  2) Error:
TestProcess#test_status_quit:
Timeout::Error: execution of assert_in_out_err expired timeout (10 sec)
pid 2682640 killed by SIGKILL (signal 9)
|-
    /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:1446:in `block in test_status_quit'
    /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:37:in `block (2 levels) in with_tmpchdir'
    /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:36:in `chdir'
    /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:36:in `block in with_tmpchdir'
    /builddir/build/BUILD/ruby-2.7.1/lib/tmpdir.rb:89:in `mktmpdir'
    /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:34:in `with_tmpchdir'
    /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:1445:in `test_status_quit'
```


```
  3) Error:
TestRubyOptions#test_segv_test:
Timeout::Error: execution of assert_in_out_err expired timeout (10 sec)
pid 2683275 killed by SIGABRT (signal 6) (core dumped)
```

```
  1) Error:
TestRubyOptions#test_segv_loaded_features:
Timeout::Error: execution of assert_in_out_err expired timeout (10 sec)
pid 2181948 killed by SIGKILL (signal 9)
|-
| -e:1: [BUG] Segmentation fault at 0x00214b3c000003e8
```

```
  2) Error:
TestRubyOptions#test_segv_setproctitle:
Timeout::Error: execution of assert_in_out_err expired timeout (10 sec)
pid 2181951 killed by SIGKILL (signal 9)
|-
| -e:1: [BUG] Segmentation fault at 0x00214b3f000003e8
```

```
  1) Error:
TestSignal#test_ignored_interrupt:
Timeout::Error: execution of assert_in_out_err expired timeout (10 sec)
pid 2032663 killed by SIGKILL (signal 9)
| 
    /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_signal.rb:294:in `test_ignored_interrupt'
Finished tests in 564.613810s, 37.2130 tests/s, 4826.1873 assertions/s.
```





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

  parent reply	other threads:[~2020-07-23 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 12:06 [ruby-core:98569] [Ruby master Bug#16921] s390x: ramdom test failures for timeout or segmentation fault jaruga
2020-05-29 12:22 ` [ruby-core:98570] [Ruby master Bug#16921] s390x: random " mame
2020-05-29 20:00 ` [ruby-core:98577] " jaruga
2020-06-18 17:13 ` [ruby-core:98873] " v.ondruch
2020-07-23 15:06 ` [ruby-core:99299] " jaruga
2020-07-23 19:28 ` jaruga [this message]
2020-07-28  6:55 ` [ruby-core:99366] " jaruga
2021-06-16  9:12 ` [ruby-core:104302] " jaruga
2021-06-16  9:15 ` [ruby-core:104303] " jaruga

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=redmine.journal-86694.20200723192830.11018@ruby-lang.org \
    --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).