Issue #7681 has been updated by luislavena (Luis Lavena).

Priority changed from High to Urgent

Ping?

Failed test might indicate something is not working as expected or test is doing something incorrectly.

This failed test is blocking automated builds that are provided to Windows users that want to try out Ruby 2.0 prior to the official release.

Not having automated builds will hit us hard as possible bugs are left uncovered in other platforms.

Please let me know if it is possible for you to review your change or someone else should be doing it.

Thank you.
----------------------------------------
Bug #7681: Flip-flop test failure under MinGW
https://bugs.ruby-lang.org/issues/7681#change-35367

Author: luislavena (Luis Lavena)
Status: Assigned
Priority: Urgent
Assignee: nobu (Nobuyoshi Nakada)
Category: test
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2013-01-11 trunk 38770) [x64-mingw32]


Hello,

Since r38747 test_shared_thread is failing under both x86 and x64 MinGW (GCC 4.7.2):

http://ci.rubyinstaller.org/view/All/job/ruby-trunk-x86-test-all/669/console

http://ci.rubyinstaller.org/view/All/job/ruby-trunk-x64-test-all/545/console

  1) Failure:
test_shared_thread(TestFlip) [C:/Users/Worker/Jenkins/workspace/ruby-trunk-x86-build/test/ruby/test_flip.rb:40]:
flip-flop should be separated per threads.
<[3, 4, 5]> expected but was
<[3, 4]>.



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