Bug #1500: test_io runs forever in windows

• Status: Third Party's Issue
• Assignee: nobu (Nobuyoshi Nakada)
• Target version: 1.9.2
• ruby -v: TRUNK

[rogerdpack (Roger Pack)]

=begin
Don't know if this is expected, but running

loop {a << IO.pipe; }

runs forever in windows (from test_dup_many).
Thanks!
-=r
=end

[jonco (Jon Coppeard)]

=begin
I am seeing this too.

Ruby version: ruby-1.9.1-p129
Cygwin version: CYGWIN_NT-5.1 1.5.25(0.156/4/2) 2008-06-12 19:34
Windows version: Windows XP Professional Ver 5.1 Build 2600 Service Pack 2

If I remove test_io, then all other tests pass.

Cheers,

Jon
=end

[rogerdpack (Roger Pack)]

=begin

If I remove test_io, then all other tests pass.

They all pass? no failures?
Thanks.
-=r
=end

[yugui (Yuki Sonoda)]

• Assignee set to usa (Usaku NAKAMURA)
• Target version set to 1.9.2

=begin

=end

[usa (Usaku NAKAMURA)]

• Assignee changed from usa (Usaku NAKAMURA) to nobu (Nobuyoshi Nakada)

=begin
cygwin.
=end

[rogerdpack (Roger Pack)]

=begin
Note that this occurs on non cygwin as well.
=end

[hperkins (Hal Perkins)]

=begin
Also observed on Mac OS X 10.5.7 with Ruby 1.9.1-p243. After building with defaults (no options to configure or make), all tests pass except for #226, test_io.rb. That test fails with the message "not finished in 10 seconds [ruby-dev:32566]"
=end

[rogerdpack (Roger Pack)]

=begin
Turns out not to be that

loop {a << IO.pipe; }

runs forever in mingw, but that IO#dup in mingw hangs the process if it is called once, fails, and is called again (same fd).
I'm going to ping the mingw people about it.
Until then could someone please apply the patch to add a timeout, from 373? Otherwise make test-all hangs in mingw.
Thanks!
-r
=end

[rogerdpack (Roger Pack)]

• Status changed from Open to Third Party's Issue

=begin
Turns out to be a bug in msvcrt.dll [I think].
=end