[ http://jira.codehaus.org/browse/CONTINUUM-968?page=comments#action_79068 
] 
            
Baerrach bonDierne commented on CONTINUUM-968:
----------------------------------------------

I'm working off HEAD (revision 470234) with a local snapshot build of 
maven-release-manager.
Windows XP (no cygwin)

Trying mvn clean install from project root fails at continuum-release with the 
reason that:
{noformat}
junit.framework.AssertionFailedError: Test released version
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at 
org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.releaseSimpleProject(ReleaseTaskExecutorTest.java:111)
at 
org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleases(ReleaseTaskExecutorTest.java:115)
{noformat}

If go into the continuum-release module and run mvn clean it will sometimes 
work and sometimes fail with the same error.

Because this error is intermittent it feels like a timing issue with the 
Microsoft clock not being accurate enough. If I remember rightly it is only 
even milliseconds or something.  This might be causing the issue with the tests.
I remember that "mvn release:prepare" had similar issues too.



> Tests for continuum-release fail randomly
> -----------------------------------------
>
>                 Key: CONTINUUM-968
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-968
>             Project: Continuum
>          Issue Type: Test
>    Affects Versions: 1.1
>         Environment: tests fail for some environments and pass for others. 
> For some they fail at random
>            Reporter: Philippe Faes
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: continuum-release.diff
>
>
> The test for continuum-release fails randomly. This is because the two test 
> methods are executed in a random order (this is intended JUnit behavior), and 
> the tests alter files. 
> Solution is to restore files between tests (method setUp) and to force the 
> order of the two tests (create one test method that calls the two other 
> methods one by one).
> Patch is attached. Please verify and commit.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to