Project

General

Profile

Actions

Bug #8408

closed

minitest's test may fail randomly

Bug #8408: minitest's test may fail randomly

Added by naruse (Yui NARUSE) over 12 years ago. Updated over 12 years ago.

Status:
Closed
Target version:
ruby -v:
ruby 2.1.0dev (2013-05-15 trunk 40752) [x86_64-freebsd9.1]
[ruby-core:54997]

Description

test/minitest/test_minitest_spec.rb may fail as following:
http://c5664.rubyci.org/~chkbuild/ruby-trunk/log/20130515T013301Z.log.html.gz

  1. Failure:
    TestMeta#test_structure_subclasses [/home/chkbuild/build/20130515T013301Z/ruby/test/minitest/test_minitest_spec.rb:751]:
    Expected #<#Class:0x002abd3bcfd7f8:0x002abd3bf000f0 @name=nil, @io=nil, @passed=nil> (top-level thingy::inner) to respond to #xyz.

  2. Failure:
    TestMeta#test_name [/home/chkbuild/build/20130515T013301Z/ruby/test/minitest/test_minitest_spec.rb:668]:
    Expected: "ExampleA"
    Actual: "top-level thingy::ExampleA"

  3. Failure:
    TestMeta#test_structure [/home/chkbuild/build/20130515T013301Z/ruby/test/minitest/test_minitest_spec.rb:687]:
    --- expected
    +++ actual
    @@ -1 +1 @@
    -"top-level thingy"
    +"top-level thingy::top-level thingy"

  4. Failure:
    TestMeta#test_name2 [/home/chkbuild/build/20130515T013301Z/ruby/test/minitest/test_minitest_spec.rb:680]:
    Expected: "ExampleA"
    Actual: "top-level thingy::ExampleA"

It seems because of minitest's bug.
minitest's parallelize_me! make tests parallell but its describe method uses single stack.

Updated by naruse (Yui NARUSE) over 12 years ago Actions #1 [ruby-core:55553]

  • Priority changed from Normal to 5

Updated by zenspider (Ryan Davis) over 12 years ago Actions #2 [ruby-core:55585]

  • Status changed from Assigned to Closed
  • Priority changed from 5 to Normal

This is not high priority.

This should be fixed with import of 4.7.5.

Updated by naruse (Yui NARUSE) over 12 years ago Actions #3 [ruby-core:55595]

zenspider (Ryan Davis) wrote:

This is not high priority.

This should be fixed with import of 4.7.5.

Random test failure disturbs CI.
If you think such bug is low priority, this is not so low.
It is why I changed the priority.

Anyway thank you for r41553.

Actions

Also available in: PDF Atom