https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112020-05-29T12:08:02ZRuby Issue Tracking SystemRuby master - Bug #16921: s390x: random test failures for timeout or segmentation faulthttps://bugs.ruby-lang.org/issues/16921?journal_id=858652020-05-29T12:08:02Zjaruga (Jun Aruga)
<ul><li><strong>Subject</strong> changed from <i>s390x: ramdom test failures for timeout or segmentation fault</i> to <i>s390x: random test failures for timeout or segmentation fault</i></li></ul> Ruby master - Bug #16921: s390x: random test failures for timeout or segmentation faulthttps://bugs.ruby-lang.org/issues/16921?journal_id=858662020-05-29T12:22:51Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><p>Try an environment variable <code>RUBY_TEST_TIMEOUT_SCALE</code>. If you set <code>RUBY_TEST_TIMEOUT_SCALE=10</code>, all timeout tests wait 10 times longer.</p> Ruby master - Bug #16921: s390x: random test failures for timeout or segmentation faulthttps://bugs.ruby-lang.org/issues/16921?journal_id=858882020-05-29T20:00:43Zjaruga (Jun Aruga)
<ul></ul><p>Thanks for the info! I will try the environment variable, and will let you know here.</p> Ruby master - Bug #16921: s390x: random test failures for timeout or segmentation faulthttps://bugs.ruby-lang.org/issues/16921?journal_id=862452020-06-18T17:13:08Zvo.x (Vit Ondruch)v.ondruch@tiscali.cz
<ul></ul><p>I think there is combination of two issues. There is possibly bug in <code>EnvUtil.invoke_ruby</code> <a href="https://github.com/ruby/ruby/blob/adbdf11f94afd52d276c7891515e0eb808f6003f/tool/lib/envutil.rb#L125" class="external">1</a>, which cannot properly handle failures caused by allocation in sigsev handler. I mildly remember I was trying to debug the issue, because the <code>TestRubyOptions#test_segv_setproctitle</code> error is nothing new: <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: TestRubyOptions#test_segv_setproctitle segfaults on AARCH64 (Closed)" href="https://bugs.ruby-lang.org/issues/13758">#13758</a></p> Ruby master - Bug #16921: s390x: random test failures for timeout or segmentation faulthttps://bugs.ruby-lang.org/issues/16921?journal_id=866872020-07-23T15:06:50Zjaruga (Jun Aruga)
<ul></ul><blockquote>
<p>Try an environment variable RUBY_TEST_TIMEOUT_SCALE. If you set RUBY_TEST_TIMEOUT_SCALE=10, all timeout tests wait 10 times longer.</p>
</blockquote>
<p>Sorry for late response. I confirmed the environment variable improves. You can see <a href="https://bugs.ruby-lang.org/issues/16492#note-8" class="external">https://bugs.ruby-lang.org/issues/16492#note-8</a> for detail.</p>
<p>By the way, I would like to show the existing related issues here again.</p>
<ul>
<li>TestBugReporter#test_bug_reporter_add <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: TestBugReporter#test_bug_reporter_add test failures (Closed)" href="https://bugs.ruby-lang.org/issues/16492">#16492</a></li>
<li>TestRubyOptions#test_segv_setproctitle <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: TestRubyOptions#test_segv_setproctitle segfaults on AARCH64 (Closed)" href="https://bugs.ruby-lang.org/issues/13758">#13758</a></li>
</ul> Ruby master - Bug #16921: s390x: random test failures for timeout or segmentation faulthttps://bugs.ruby-lang.org/issues/16921?journal_id=866942020-07-23T19:28:30Zjaruga (Jun Aruga)
<ul></ul><p>I sent this PR related to this ticket.<br>
<a href="https://github.com/ruby/ruby/pull/3354" class="external">https://github.com/ruby/ruby/pull/3354</a></p>
<p>It's to apply test-scale to test_nogvl_poll.<br>
Other tests I showed above is applying time-scale.</p>
<p>I ran the Ruby tests with <code>RUBY_TEST_TIMEOUT_SCALE=100 make check</code> 5 times on Fedora build system s390x . And all ok.<br>
So, I am okay to close this ticket.</p> Ruby master - Bug #16921: s390x: random test failures for timeout or segmentation faulthttps://bugs.ruby-lang.org/issues/16921?journal_id=867692020-07-28T06:55:24Zjaruga (Jun Aruga)
<ul></ul><p>Can we apply <a href="https://bugs.ruby-lang.org/attachments/8500" class="external">the patch</a> mentioned at <a href="https://bugs.ruby-lang.org/issues/16492#note-11" class="external">https://bugs.ruby-lang.org/issues/16492#note-11</a> to the following tests using <code>assert_in_out_err</code> in those too?</p>
<ul>
<li>TestProcess#test_status_quit</li>
<li>TestRubyOptions#test_segv_test</li>
<li>TestRubyOptions#test_segv_loaded_features</li>
<li>TestRubyOptions#test_segv_setproctitle</li>
<li>TestSignal#test_ignored_interrupt</li>
</ul> Ruby master - Bug #16921: s390x: random test failures for timeout or segmentation faulthttps://bugs.ruby-lang.org/issues/16921?journal_id=925242021-06-16T09:12:03Zjaruga (Jun Aruga)
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>I have not seen this issue for a while on the Fedora s390x build server. I also have not seen it on Travis s390x pipeline and our s390x server. So, I would close this for now.</p> Ruby master - Bug #16921: s390x: random test failures for timeout or segmentation faulthttps://bugs.ruby-lang.org/issues/16921?journal_id=925252021-06-16T09:15:11Zjaruga (Jun Aruga)
<ul></ul><p>If someone will still see the issue, please let us know.</p>