On Sat, Nov 22, 2008 at 8:46 AM, sebb <[EMAIL PROTECTED]> wrote: > On 22/11/2008, Rahul Akolkar <[EMAIL PROTECTED]> wrote: <snip/> >> >> I've been nudged before, but I'm OK with it being there. >> > > OK by me too, so long as they are up to date, so I just ran a "maven > test" and it completed successfully, and the same number of tests > (228) was run, so I guess that's OK > <snap/>
Its upto date. > However, I also just ran "mvn test" again, and it failed with: > > ------------------------------------------------------------------------------- > Test set: org.apache.commons.scxml.model.ModelTestSuite > ------------------------------------------------------------------------------- > Tests run: 78, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.641 > sec <<< FAILURE! > testDatamodelNamespacePrefixedXPaths(org.apache.commons.scxml.model.DatamodelTest) > Time elapsed: 0.188 sec <<< FAILURE! > junit.framework.AssertionFailedError > at junit.framework.Assert.fail(Assert.java:47) > at > org.apache.commons.scxml.model.DatamodelTest.fireEvent(DatamodelTest.java:195) > at > org.apache.commons.scxml.model.DatamodelTest.runtest(DatamodelTest.java:150) > at > org.apache.commons.scxml.model.DatamodelTest.testDatamodelNamespacePrefixedXPaths(DatamodelTest.java:114) > > The next 2 runs succeeded. > There may be a timing error in that test - and it would help if the > fail message gave a bit more information. > <snip/> Haven't seen that before. While it shouldn't matter, I usually clean the previous build before switching (so, 'maven test' -> 'maven clean' -> 'mvn test'). -Rahul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
