maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse McConnell (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (CONTINUUM-1356) intermittent (machine wise) test failure on trunk
Date Wed, 01 Aug 2007 18:59:13 GMT

     [ http://jira.codehaus.org/browse/CONTINUUM-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jesse McConnell closed CONTINUUM-1356.
--------------------------------------

         Assignee: Jesse McConnell
       Resolution: Fixed
    Fix Version/s: 1.1-beta-2

svn commit: r561907

there was a 1.1-SNAPSHOT parent reference in a test pom...and when we left the 1.1-SNAPSHOT
version it started failing if you didn't have that 1.1-SNAPSHOT continuum parent version in
your local repo

changed it to 1.0.3 so this shouldn't happen again...all the others were fine, looks like
this one was missed sometime in the past 

> intermittent (machine wise) test failure on trunk
> -------------------------------------------------
>
>                 Key: CONTINUUM-1356
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1356
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core - Profiles
>    Affects Versions: 1.1-beta-1
>            Reporter: Jesse McConnell
>            Assignee: Jesse McConnell
>             Fix For: 1.1-beta-2
>
>
> I have been noticing an odd test case that has been failing on certain machines but have
been unable to reproduce it locally on my dev box.
> Working on a fresh installation on a friends machine I was able to find and maybe isolate
the error with some more output.
> Maybe the profile work lately has caused this to happen but some of us have something
installed in our local repo's that suppress the problem.  It  looks to me that the creation
of a project with a bogus module definition is adding an additional error to the building
results on these machines and with this output we can see that its not the /test-classes/projects/continuum/pom.xml
artifact causing the problem but the I'm-not-here-project one.
> I am making this issue so we have a bit of a record on it and maybe we can track down
why this doesn't manifest on installations such as mine (and I think emm as well)
> [INFO] Downloading file:/home/jjchapman/src/trunks/continuum/continuum-core/targ
> et/test-classes/projects/continuum/pom.xml
> [INFO] Downloading file:/home/jjchapman/src/trunks/continuum/continuum-core/targ
> et/test-classes/projects/continuum/continuum-core/pom.xml
> [INFO] Downloading file:/home/jjchapman/src/trunks/continuum/continuum-core/targ
> et/test-classes/projects/continuum/continuum-model/pom.xml
> [INFO] Downloading file:/home/jjchapman/src/trunks/continuum/continuum-core/targ
> et/test-classes/projects/continuum/continuum-plexus-application/pom.xml
> [INFO] Downloading file:/home/jjchapman/src/trunks/continuum/continuum-core/targ
> et/test-classes/projects/continuum/continuum-web/pom.xml
> [INFO] Downloading file:/home/jjchapman/src/trunks/continuum/continuum-core/targ
> et/test-classes/projects/continuum/continuum-xmlrpc/pom.xml
> [INFO] Downloading file:/home/jjchapman/src/trunks/continuum/continuum-core/targ
> et/test-classes/projects/continuum/continuum-notifiers/pom.xml
> [INFO] Downloading file:/home/jjchapman/src/trunks/continuum/continuum-core/targ
> et/test-classes/projects/continuum/I'm-not-here-project/pom.xml
> add.project.artifact.not.found.error
> add.project.missing.pom.error
> [ stderr ] ---------------------------------------------------------------
> [ stacktrace ] -----------------------------------------------------------
> junit.framework.AssertionFailedError: expected:<1> but was:<2>
>         at junit.framework.Assert.fail(Assert.java:47)
>         at junit.framework.Assert.failNotEquals(Assert.java:282)
>         at junit.framework.Assert.assertEquals(Assert.java:64)
>         at junit.framework.Assert.assertEquals(Assert.java:201)
>         at junit.framework.Assert.assertEquals(Assert.java:207)
>         at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumPro
> jectBuilderTest.testCreateProjectsWithModules(MavenTwoContinuumProjectBuilderTes
> t.java:200)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at junit.framework.TestCase.runTest(TestCase.java:154)
>         at junit.framework.TestCase.runBare(TestCase.java:127)
>         at junit.framework.TestResult$1.protect(TestResult.java:106)
>         at junit.framework.TestResult.runProtected(TestResult.java:124)
>         at junit.framework.TestResult.run(TestResult.java:109)
>         at junit.framework.TestCase.run(TestCase.java:118)
>         at junit.framework.TestSuite.runTest(TestSuite.java:208)
>         at junit.framework.TestSuite.run(TestSuite.java:203)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)

-- 
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

        

Mime
View raw message