You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2010/01/06 18:07:54 UTC

[jira] Resolved: (BUILDR-359) Buildr incorrectly reports test failures with ScalaTest 1.0.1

     [ https://issues.apache.org/jira/browse/BUILDR-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Boisvert resolved BUILDR-359.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.3.5)
                   1.4

> Buildr incorrectly reports test failures with ScalaTest 1.0.1
> -------------------------------------------------------------
>
>                 Key: BUILDR-359
>                 URL: https://issues.apache.org/jira/browse/BUILDR-359
>             Project: Buildr
>          Issue Type: Bug
>          Components: Test frameworks
>    Affects Versions: 1.3.5
>         Environment: 1.0.1-for-scala-2.8.0.Beta1-RC5-with-test-interfaces-0.2-SNAPSHOT, Scala 2.8 RC6, ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32]
>            Reporter: Travis Schneeberger
>             Fix For: 1.4
>
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> Buildr incorrectly determines when the unit tests are done because ScalaCheck changed it's completed output string.  I've trace the bug to the following file:
> buildr-1.3.5-x86-mswin32\lib\buildr\scala\tests.rb
> See the patch below for details
> 130c130
> <               completed |= (line =~ /Run completed/)
> ---
> >               completed |= (line =~ /Run completed\./)
> In case it's not obvious, I removed a \. from the end of the regex string.  Enjoy!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.