You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by Thomas Engelschmidt <te...@zama.org> on 2008/07/09 15:53:43 UTC
junit test failure
Hi,
I have just checkout the main trunk from svn.apache.org and it
compiles fine, but
when running ant tests;
Junit has 16 failures, should I create an jira issue for each failed
testcase ?
:
com.ecyrd.jspwiki.content 19 0 2 3.556 2008-07-09T13:17:25 Zama-3.local
com.ecyrd.jspwiki.parser 409 0 8 28.375 2008-07-09T13:17:43 Zama-3.local
com.ecyrd.jspwiki.providers 46 0 5 40.335 2008-07-09T13:18:30
Zama-3.local
stress 1 0 1 112.147 2008-07-09T13:20:16 Zama-3.local
cheers
Thomas
Building on :
OS : OS X
Java :
java version "1.6.0_04-dp"
Java(TM) SE Runtime Environment (build 1.6.0_04-dp-b06-110)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_04-b12-45-optimized,
mixed mode)
Re: junit test failure
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
Anyhoo, as of the latest commit, all of the tests run barring two in
PageRenamer (where help would be appreciated).
/Janne
On Jul 10, 2008, at 09:40 , Janne Jalkanen wrote:
>
> I am, of course, seeing only twelve...
>
> The PageRenamer failures are real. The parser ones seem to be
> coming from CSS tweaks (Dirk, please run unit tests when changing
> the code!)
>
> /Janne
>
> On Jul 9, 2008, at 22: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
Re: junit test failure
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
I am, of course, seeing only twelve...
The PageRenamer failures are real. The parser ones seem to be coming
from CSS tweaks (Dirk, please run unit tests when changing the code!)
/Janne
On Jul 9, 2008, at 22: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
Re: junit test failure
Posted by Andrew Jaquith <an...@mac.com>.
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
>>>
>>
>
Re: junit test failure
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
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
>>
>
Re: junit test failure
Posted by Thomas Engelschmidt <te...@zama.org>.
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
>
Re: junit test failure
Posted by Andrew Jaquith <an...@mac.com>.
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
Re: junit test failure
Posted by Janne Jalkanen <ja...@iki.fi>.
> 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