Thanks!
Other than the 2 persistent PageRenamer failures, tests are running
100% clean for me. Excellent.
Andrew
On Jul 10, 2008, at 12:16 PM, Janne Jalkanen wrote:
I checked, it didn't clear the repo properly previously, so it would
fail if you had any files lying around from an old run. So it was
completely dependent on the running order :-)
I'm committing a fix soon once I get all of the stress tests run.
/Janne
On Jul 10, 2008, at 17:11 , Thomas Engelschmidt wrote:
Hi
The stess test is still failing for me
Cheers
/Thomas
Name Status Type Time(s)
testMassiveRepository1 Failure Right number of pages
expected:<1000> but was:<1001>
junit.framework.AssertionFailedError: Right number of pages
expected:<1000> but was:<1001>
at
stress
.MassiveRepositoryTest
.testMassiveRepository1(MassiveRepositoryTest.java:109)
107.338
On Jul 9, 2008, at 21:50 , Andrew Jaquith wrote:
My last Junit test run had identical results: 16 failures, and all
in the same places.
On Jul 9, 2008, at 11:14 AM, Janne Jalkanen wrote:
Junit has 16 failures, should I create an jira issue for each
failed
testcase ?
Hi!
No need, these are easily reproducible for us. Besides, there are
often cases where a simple misconfig or a typo can cause massive
breakage, and we'll just be outflooded completely with JIRA
issues ;-)
You can send patches to the mailing list though, or if you've
developed a patch for something, you can then open up a JIRA issue.
If a testcase keeps failing for several builds, then it's likely
that
there's something complicated afoot.
/Janne
