ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
* [ruby-core:98569] [Ruby master Bug#16921] s390x: ramdom test failures for timeout or segmentation fault
@ 2020-05-29 12:06 jaruga
  2020-05-29 12:22 ` [ruby-core:98570] [Ruby master Bug#16921] s390x: random " mame
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: jaruga @ 2020-05-29 12:06 UTC (permalink / raw)
  To: ruby-core

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

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

* 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/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [ruby-core:98570] [Ruby master Bug#16921] s390x: random test failures for timeout or segmentation fault
  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 ` mame
  2020-05-29 20:00 ` [ruby-core:98577] " jaruga
                   ` (6 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: mame @ 2020-05-29 12:22 UTC (permalink / raw)
  To: ruby-core

Issue #16921 has been updated by mame (Yusuke Endoh).


Try an environment variable `RUBY_TEST_TIMEOUT_SCALE`.  If you set `RUBY_TEST_TIMEOUT_SCALE=10`, all timeout tests waits 10 times longer.

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

* 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/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [ruby-core:98577] [Ruby master Bug#16921] s390x: random test failures for timeout or segmentation fault
  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 ` jaruga
  2020-06-18 17:13 ` [ruby-core:98873] " v.ondruch
                   ` (5 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: jaruga @ 2020-05-29 20:00 UTC (permalink / raw)
  To: ruby-core

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


Thanks for the info! I will try the environment variable, and will let you know here.


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

* 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/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [ruby-core:98873] [Ruby master Bug#16921] s390x: random test failures for timeout or segmentation fault
  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 ` v.ondruch
  2020-07-23 15:06 ` [ruby-core:99299] " jaruga
                   ` (4 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: v.ondruch @ 2020-06-18 17:13 UTC (permalink / raw)
  To: ruby-core

Issue #16921 has been updated by vo.x (Vit Ondruch).


I think there is combination of two issues. There is possibly bug in `EnvUtil.invoke_ruby` [1], which cannot properly handle failures caused by allocation in sigsev handler. I mildly remember I was trying to debug the issue, because the `TestRubyOptions#test_segv_setproctitle` error is nothing new: #13758 


[1]: https://github.com/ruby/ruby/blob/adbdf11f94afd52d276c7891515e0eb808f6003f/tool/lib/envutil.rb#L125

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

* 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/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [ruby-core:99299] [Ruby master Bug#16921] s390x: random test failures for timeout or segmentation fault
  2020-05-29 12:06 [ruby-core:98569] [Ruby master Bug#16921] s390x: ramdom test failures for timeout or segmentation fault jaruga
                   ` (2 preceding siblings ...)
  2020-06-18 17:13 ` [ruby-core:98873] " v.ondruch
@ 2020-07-23 15:06 ` jaruga
  2020-07-23 19:28 ` [ruby-core:99305] " jaruga
                   ` (3 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: jaruga @ 2020-07-23 15:06 UTC (permalink / raw)
  To: ruby-core

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


> Try an environment variable RUBY_TEST_TIMEOUT_SCALE. If you set RUBY_TEST_TIMEOUT_SCALE=10, all timeout tests wait 10 times longer.

Sorry for late response. I confirmed the environment variable improves. You can see https://bugs.ruby-lang.org/issues/16492#note-8 for detail.

By the way, I would like to show the existing related issues here again.

* TestBugReporter#test_bug_reporter_add #16492
* TestRubyOptions#test_segv_setproctitle #13758






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

* 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/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [ruby-core:99305] [Ruby master Bug#16921] s390x: random test failures for timeout or segmentation fault
  2020-05-29 12:06 [ruby-core:98569] [Ruby master Bug#16921] s390x: ramdom test failures for timeout or segmentation fault jaruga
                   ` (3 preceding siblings ...)
  2020-07-23 15:06 ` [ruby-core:99299] " jaruga
@ 2020-07-23 19:28 ` jaruga
  2020-07-28  6:55 ` [ruby-core:99366] " jaruga
                   ` (2 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: jaruga @ 2020-07-23 19:28 UTC (permalink / raw)
  To: ruby-core

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/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [ruby-core:99366] [Ruby master Bug#16921] s390x: random test failures for timeout or segmentation fault
  2020-05-29 12:06 [ruby-core:98569] [Ruby master Bug#16921] s390x: ramdom test failures for timeout or segmentation fault jaruga
                   ` (4 preceding siblings ...)
  2020-07-23 19:28 ` [ruby-core:99305] " jaruga
@ 2020-07-28  6:55 ` jaruga
  2021-06-16  9:12 ` [ruby-core:104302] " jaruga
  2021-06-16  9:15 ` [ruby-core:104303] " jaruga
  7 siblings, 0 replies; 9+ messages in thread
From: jaruga @ 2020-07-28  6:55 UTC (permalink / raw)
  To: ruby-core

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


Can we apply [the patch](https://bugs.ruby-lang.org/attachments/8500) mentioned at https://bugs.ruby-lang.org/issues/16492#note-11 to the following tests using `assert_in_out_err` in those too?

* TestProcess#test_status_quit
* TestRubyOptions#test_segv_test
* TestRubyOptions#test_segv_loaded_features
* TestRubyOptions#test_segv_setproctitle
* TestSignal#test_ignored_interrupt


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

* 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/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [ruby-core:104302] [Ruby master Bug#16921] s390x: random test failures for timeout or segmentation fault
  2020-05-29 12:06 [ruby-core:98569] [Ruby master Bug#16921] s390x: ramdom test failures for timeout or segmentation fault jaruga
                   ` (5 preceding siblings ...)
  2020-07-28  6:55 ` [ruby-core:99366] " jaruga
@ 2021-06-16  9:12 ` jaruga
  2021-06-16  9:15 ` [ruby-core:104303] " jaruga
  7 siblings, 0 replies; 9+ messages in thread
From: jaruga @ 2021-06-16  9:12 UTC (permalink / raw)
  To: ruby-core

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

Status changed from Open to Closed

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.


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

* Author: jaruga (Jun Aruga)
* Status: Closed
* 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/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [ruby-core:104303] [Ruby master Bug#16921] s390x: random test failures for timeout or segmentation fault
  2020-05-29 12:06 [ruby-core:98569] [Ruby master Bug#16921] s390x: ramdom test failures for timeout or segmentation fault jaruga
                   ` (6 preceding siblings ...)
  2021-06-16  9:12 ` [ruby-core:104302] " jaruga
@ 2021-06-16  9:15 ` jaruga
  7 siblings, 0 replies; 9+ messages in thread
From: jaruga @ 2021-06-16  9:15 UTC (permalink / raw)
  To: ruby-core

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


If someone will still see the issue, please let us know.


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

* Author: jaruga (Jun Aruga)
* Status: Closed
* 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/

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2021-06-16  9:15 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 ` [ruby-core:99305] " jaruga
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

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).