[MinGW] Unexpected close program dialog for TestRubyOptions#test_segv_test
While running tests for MinGW-based build of trunk, I've found the mentioned test (test_segv_test) always blocks test execution.
The command issue to trigger this was:
make test-all TESTS="-q -v ruby/test_rubyoptions.rb -n test_segv_test"
Which triggers a Windows dialog indicating the failure (see attached)
And the following backtrace:
IOError: stream closed
read'block in invoke_ruby'
1 tests, 0 assertions, 0 failures, 1 errors, 0 skips
Is this issue also showing on mswin builds? This seems to be a blocker for running continuous integration tests as the crash dialog needs to be closed manually.
#1 [ruby-core:45412] Updated by Hiroshi Shirosaki over 4 years ago
I saw similar blocking issues with the following tests while MinGW test-all, but mswin build doesn't have.
test_segv_test in ruby/test_rubyoptions.rb
test_require_invalid_shared_object in ruby/test_require.rb.
test_separate in test/testunit/test_parallel.rb
Modifying registry value as below works fine for me on Win7.
Modify ErrorMode value to
The following command will complete with mingw build.
make test-all TESTS="-qv -j2"
#3 Updated by Nobuyoshi Nakada over 4 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
This issue was solved with changeset r35913.
Luis, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
no windows dialog
- win32/win32.c (rb_w32_sysinit): let the system not display the critical-error-handler message box and the Windows Error Reporting dialog. [Bug #6535]