From: "usa (Usaku NAKAMURA)" Date: 2012-06-04T13:14:06+09:00 Subject: [ruby-core:45413] [ruby-trunk - Bug #6535] [MinGW] Unexpected close program dialog for TestRubyOptions#test_segv_test Issue #6535 has been updated by usa (Usaku NAKAMURA). Assignee changed from usa (Usaku NAKAMURA) to nobu (Nobuyoshi Nakada) So, this is mingw issue, I guess. ---------------------------------------- Bug #6535: [MinGW] Unexpected close program dialog for TestRubyOptions#test_segv_test https://bugs.ruby-lang.org/issues/6535#change-27001 Author: luislavena (Luis Lavena) Status: Assigned Priority: Normal Assignee: nobu (Nobuyoshi Nakada) Category: build Target version: 2.0.0 ruby -v: ruby 2.0.0dev (2012-06-02 trunk 35867) [i386-mingw32] =begin Hello, 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: test_segv_test(TestRubyOptions): IOError: stream closed C:/Users/Worker/Code/ruby/ruby/test/ruby/envutil.rb:60:in `read' C:/Users/Worker/Code/ruby/ruby/test/ruby/envutil.rb:60:in `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. Thank you. =end -- http://bugs.ruby-lang.org/