Issue #14906 has been updated by MSP-Greg (Greg L).


normalperson (Eric Wong) wrote:

>  Oops, sorry about that :x

No problem.  I don't expect you or anyone else to know Windows.  I'm well aware that the vast majority of production Ruby apps don't run on Windows.

It wasn't that long ago when there was no real testing of Windows builds.  Now, mswin & mingw normally pass all tests.  Thanks to you and everyone else...

Anyway, would a summary of all tests that failed/errored during parallel testing but passed during 'retry' be helpful?  I've got all the build logs saved locally, so I can go back quite a few builds...

Thanks, Greg


----------------------------------------
Bug #14906: MinGW failure - TestIO#test_copy_stream_no_busy_wait
https://bugs.ruby-lang.org/issues/14906#change-72927

* 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>