You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-dev@jackrabbit.apache.org by bu...@apache.org on 2013/06/13 17:57:17 UTC

buildbot failure in ASF Buildbot on oak-trunk

The Buildbot has detected a new failure on builder oak-trunk while building ASF Buildbot.
Full details are available at:
 http://ci.apache.org/builders/oak-trunk/builds/2665

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: osiris_ubuntu

Build Reason: scheduler
Build Source Stamp: [branch jackrabbit/oak/trunk] 1492716
Blamelist: mduerig

BUILD FAILED: failed compile

sincerely,
 -The Buildbot

Re: buildbot failure in ASF Buildbot on oak-trunk

Posted by Jukka Zitting <ju...@gmail.com>.

Hi,

On Thu, Jun 13, 2013 at 7:42 PM, Michael Dürig <md...@apache.org> wrote:
> Why are we mixing Junit3 and Junit4 style test cases anyway?

Good question. AFAICT most of the JUnit 3 usage comes from extending
(through various intermediaries) the AbstractJCRTest class from
jackrabbit-jcr-tests.

In such cases it would be clearer if people didn't use the JUnit 4
@Test annotations, as the JUnit 3 testXXX() naming pattern is
sufficient for test cases in classes that extend TestCase.

BR,

Jukka Zitting

Re: buildbot failure in ASF Buildbot on oak-trunk

Posted by Michael Dürig <md...@apache.org>.

Forgot to add test case to the known.issues list in oak-jcr/pom.xml. 
Should be fixed at r1492748.

Why are we mixing Junit3 and Junit4 style test cases anyway?

Michael

On 13.6.13 16:57, buildbot@apache.org wrote:
> The Buildbot has detected a new failure on builder oak-trunk while building ASF Buildbot.
> Full details are available at:
>   http://ci.apache.org/builders/oak-trunk/builds/2665
>
> Buildbot URL: http://ci.apache.org/
>
> Buildslave for this Build: osiris_ubuntu
>
> Build Reason: scheduler
> Build Source Stamp: [branch jackrabbit/oak/trunk] 1492716
> Blamelist: mduerig
>
> BUILD FAILED: failed compile
>
> sincerely,
>   -The Buildbot
>
>
>