[ruby-core:55541] [ruby-trunk - Bug #8519][Assigned] Test IO Timeout error and free space starvation

Issue #8519 has been updated by h.shirosaki (Hiroshi Shirosaki).

Status changed from Closed to Assigned
Assignee changed from cruby-windows to nobu (Nobuyoshi Nakada)

test_write_32bit_boundary still fails on CI.

TestIO#test_write_32bit_boundary = 137.43 s = E

http://ci.rubyinstaller.org/job/ruby-trunk-x86-test-all/1566/console

I tried the test on my local Win7 and took about 50s to complete with changing timeout to 60s. And the test creates a 4.2GB temp file.
Since it takes very long time and fails on CI, is it better to skip the test on mingw?
----------------------------------------
Bug #8519: Test IO Timeout error and free space starvation
https://bugs.ruby-lang.org/issues/8519#change-40028

Author: luislavena (Luis Lavena)
Status: Assigned
Priority: Normal
Assignee: nobu (Nobuyoshi Nakada)
Category: test
Target version: next minor
ruby -v: ruby 2.1.0dev (2013-06-12 trunk 41250) [x64-mingw32]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN


=begin
Hello,

As originally mentioned in [ruby-core:55416], a particular test on ruby_2_0_0 branch and trunk is leaving temporary files behind and causing the CI worker to have no free space.

The failing test:

http://ci.rubyinstaller.org/job/ruby-2_0_0-x64-test-all/87/console
http://ci.rubyinstaller.org/job/ruby-trunk-x64-test-all/1371/console

   2) Error:
 TestIO#test_write_32bit_boundary:
 Timeout::Error: Timeout::Error
     C:/Users/Worker/Jenkins/workspace/ruby-trunk-x64-build/test/ruby/envutil.rb:78:in `invoke_ruby'
     C:/Users/Worker/Jenkins/workspace/ruby-trunk-x64-build/test/ruby/envutil.rb:298:in `assert_separately'
     C:/Users/Worker/Jenkins/workspace/ruby-trunk-x64-build/test/ruby/test_io.rb:2693:in `block in test_write_32bit_boundary'
     C:/Users/Worker/Jenkins/workspace/ruby-trunk-x64-build/test/ruby/test_io.rb:1247:in `make_tempfile'
     C:/Users/Worker/Jenkins/workspace/ruby-trunk-x64-build/test/ruby/test_io.rb:2692:in `test_write_32bit_boundary'

And ruby_2_0_0:

   1) Error:
 test_write_32bit_boundary(TestIO):
 Timeout::Error: Timeout::Error
     C:/Users/Worker/Jenkins/workspace/ruby-2_0_0-x64-build/test/ruby/envutil.rb:77:in `invoke_ruby'
     C:/Users/Worker/Jenkins/workspace/ruby-2_0_0-x64-build/test/ruby/envutil.rb:266:in `assert_separately'
     C:/Users/Worker/Jenkins/workspace/ruby-2_0_0-x64-build/test/ruby/test_io.rb:2674:in `block in test_write_32bit_boundary'
     C:/Users/Worker/Jenkins/workspace/ruby-2_0_0-x64-build/test/ruby/test_io.rb:1246:in `make_tempfile'
     C:/Users/Worker/Jenkins/workspace/ruby-2_0_0-x64-build/test/ruby/test_io.rb:2673:in `test_write_32bit_boundary'

The test (({test_write_32bit_boundary})) is not properly cleaning up the temporary file it creates.

This was not a problem before and just recently started to happen. It is worth to mention no change in the worker setup has been made except normal Windows security upgrades.

Ideas?
=end


-- 
http://bugs.ruby-lang.org/