From: Greg.mpls@... Date: 2018-08-29T21:05:58+00:00 Subject: [ruby-core:88741] [Ruby trunk Bug#15043] MinGW intermittent test failure - TestIO#test_select_leak Issue #15043 has been updated by MSP-Greg (Greg L). @normalperson Eric, Thanks for looking at it and also the patch. It passed test-all, but as mentioned, it's intermittent and I can't repo it with ruby-loco... Greg ---------------------------------------- Bug #15043: MinGW intermittent test failure - TestIO#test_select_leak https://bugs.ruby-lang.org/issues/15043#change-73795 * Author: MSP-Greg (Greg L) * Status: Closed * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.0dev (2018-08-29 trunk 64589) [x64-mingw32] * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- @normalperson Eric, Thought I'd ping you on this, as the test is very new. The above test is not failing on Travis Ubuntu, nor Appveyor mswin or ruby-loco. It is intermittently failing on the recently added Ruby Appveyor mingw job. Console output is: ``` 1) Failure: TestIO#test_select_leak [C:/projects/ruby/test/ruby/test_io.rb:3833]: pid 1384 exit 1 | # terminated with exception (report_on_exception is true): | select used to leak on exception (StandardError) | -: select used to leak on exception (StandardError) ``` As far as I can tell, there are two main differences between ruby mingw & ruby-loco. First, I'm passing a `-j` parameter to the test framework, Ruby mingw is passing it to the make command. Secondly, I'm updating the build system (MSYS2/MinGW), Ruby mingw is not. Appveyor can get a few months behind. I ran the test file a few times locally using runner.rb, both normal & parallel. All tests passed, two skips when run normal, eight skips when run parallel. Finally, the Appveyor VM's have two procs, I believe Travis' Vm's are four. Build/test times can vary quite a bit on Appveyor. Thanks, Greg -- https://bugs.ruby-lang.org/ Unsubscribe: