From: Greg.mpls@... Date: 2018-07-11T13:29:24+00:00 Subject: [ruby-core:87908] [Ruby trunk Bug#14906] MinGW failure - TestIO#test_copy_stream_no_busy_wait Issue #14906 has been updated by MSP-Greg (Greg L). @normalperson Eric, r63947 was causing a test-all failure, as on Windows, one can't do `File.unlink(t.path)` if t is open (or before `t.close`). I did a PR, and a moment later, @znz pushed a commit. mswin passed test-all. That was the only issue in mswin, I'll started a ruby-loco built shortly. I've always used `--show-skip`, and from time to time check the skips. It has been stable... Thanks again, Greg ---------------------------------------- Bug #14906: MinGW failure - TestIO#test_copy_stream_no_busy_wait https://bugs.ruby-lang.org/issues/14906#change-72916 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.0dev (2018-07-11 trunk 63945) [x64-mingw32] * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- ruby-loco just had a failure on `TestIO#test_copy_stream_no_busy_wait` for the first time. ``` 8) Failure: TestIO#test_copy_stream_no_busy_wait [C:/projects/ruby-loco/src/ruby/test/ruby/test_io.rb:557]: r58534 [ruby-core:80969] [Backport #13533]. Expected 0.031000000000000028 to be <= 0.016417910447761194. ``` This was on Appveyor, it passed during parallel, but failed on retry, as `TestIO#test_write_no_garbage` failed during parallel, which is common. I haven't really looked at it, or especially `assert_cpu_usage_low`, but a change to loosen the test up would be helpful. BTW, it was the only failure on r63945. I haven't really analyzed it, but Appveyor does seem slower just in the last day or so... Thanks, Greg -- https://bugs.ruby-lang.org/ Unsubscribe: