[logback-user] Building logback when tests fail

ceki ceki at qos.ch
Tue Oct 25 15:03:21 CEST 2011

On 25/10/2011 2:34 PM, Thorbjørn Ravn Andersen wrote:
> Thanks for a prompt reply.
> I am building directly from a clone of git master.  Is there a specific tag
> I should use to choose a suitable commit?

No, need to chose a special tag or commit. Clone of master should be fine.

> Maven reports:
> Tests in error:
> autoConfigFromSystemProperties(ch.qos.logback.classic.util.ContextInitialize
> rTest)


That's a lot of failures.

> Tests run: 374, Failures: 0,git  Errors: 17, Skipped: 10
> You may have forgotten to check in some files?  Have your CI-engine reported
> anything?

No, logback build on different machines. However, on busy or slow
machines build failures occur frequently. Failures in
ContextInitializerTest seem to indicate that the tests are not run in
an independent JVM. Failures in ReconfigureOnChangeTest indicate that
the tests are run on a slow/busy machine.

It sucks that logback does not build on all machines.

> If you use IDEA and it works well, I'll have a go tomorrow.  We happen to
> have a license for IntelliJ IDEA 9.

IDEA licenses are date-based, at the least the license I have is. So
you should be able to upgrade to the latest version of IDEA with your
existing license.


More information about the Logback-user mailing list