From: Koichi Sasada Date: 2018-08-07T13:11:46+09:00 Subject: [ruby-core:88321] Re: [ruby-alerts:8236] failure alert on trunk@P895 (NG (r64134)) On 2018/08/01 15:52, Eric Wong wrote: > ko1c-failure@atdot.net wrote: >> detail: https://gist.github.com/86472ce5bcef5cfdcd696ab674b0ab07 >> >> desc: >> rev: 64134 >> test-all : 20289 tests, 5128654 assertions, 0 failures, 1 errors, 65 skips >> : 1) >> : TestIO#test_race_gets_and_close: >> : Timeout::Error: execution of assert_separately expired timeout (10 sec) > >> http://ci.rvm.jp/results/trunk@P895/1174672 > > ko1: any chance this failure is a build system bug? > I'm not able to reproduce it and cannot find a cause. > > I expected r64133 to fix this; and I made r64135 to help diagnose > this in case it happens again. So far, no other failures on > test_race_gets_and_close ... Sorry I got summer vacation last week. And sorry original binary file is rewritten by next build. This CI environment repeat: "make update-download -j8" exit with 0. "make update-rubyspec -j8" exit with 0. "make update-src -j8" exit with 0. "make after-update -j8" exit with 0. "make miniruby -j8" exit with 0. "make ruby -j8" exit with 0. "make all -j8" exit with 0. "make install -j8" exit with 0. "make yes-btest TESTS='-j8'" exit with 0. "make yes-test-basic TESTS='-j8'" exit with 0. "make yes-test-all TESTS='-j8'" exit with 512. "make yes-test-rubyspec TESTS='-j8'" exit with 0. on same directory. I want to propose that `assert_separately` method invoke gdb and check stacktrace before sending TERM/KILL if gdb is available. Nobu, what do you think? -- // SASADA Koichi at atdot dot net Unsubscribe: