logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <ralph.go...@dslextreme.com>
Subject Re: buildbot exception in ASF Buildbot on log4j2-nightly
Date Sat, 29 Nov 2014 16:58:01 GMT
I am not sure why the nightly build would be building the site.

Yesterday when i saw this I performed a log4j build and it failed with the log below. I can’t
really tell what is wrong with the MarkerTest just by looking.


 T E S T S
-------------------------------------------------------
Running org.apache.logging.slf4j.CallerInformationTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.35 sec - in org.apache.logging.slf4j.CallerInformationTest
Running org.apache.logging.slf4j.LoggerTest
2014-11-28 09:19:02,994 ERROR Appenders contains an invalid element or attribute "SLF4J"
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.099 sec - in org.apache.logging.slf4j.LoggerTest
Running org.apache.logging.slf4j.MarkerTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec <<< FAILURE!
- in org.apache.logging.slf4j.MarkerTest
testMarker(org.apache.logging.slf4j.MarkerTest)  Time elapsed: 0.003 sec  <<< FAILURE!
java.lang.AssertionError: TEST (log4jMarker=TEST) is not an instance of PARENT (log4jParent=PARENT)
in Log4j
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.apache.logging.slf4j.MarkerTest.testMarker(MarkerTest.java:47)

Running org.apache.logging.slf4j.SerializeTest
2014-11-28 09:19:03,091 ERROR Appenders contains an invalid element or attribute "SLF4J"
2014-11-28 09:19:03,115 ERROR No log4j2 configuration file found. Using default configuration:
logging only errors to the console.
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec - in org.apache.logging.slf4j.SerializeTest

Results :

Failed tests: 
  MarkerTest.testMarker:47 TEST (log4jMarker=TEST) is not an instance of PARENT (log4jParent=PARENT)
in Log4j



Tests run: 16, Failures: 1, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Log4j 2 .................................... SUCCESS [17.693s]
[INFO] Apache Log4j API .................................. SUCCESS [13.940s]
[INFO] Apache Log4j Core ................................. SUCCESS [5:26.971s]
[INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [4.785s]
[INFO] Apache Log4j SLF4J Binding ........................ FAILURE [3.076s]
[INFO] Apache Log4j to SLF4J Adapter ..................... SKIPPED
[INFO] Apache Log4j Commons Logging Bridge ............... SKIPPED
[INFO] Apache Log4j Flume Bridge ......................... SKIPPED
[INFO] Apache Log4j Web .................................. SKIPPED
[INFO] Apache Log4j Tag Library .......................... SKIPPED
[INFO] Apache Log4j JMX GUI .............................. SKIPPED
[INFO] Apache Log4j Samples .............................. SKIPPED
[INFO] Apache Log4j Samples: Flume - Common .............. SKIPPED
[INFO] Apache Log4j Samples: Flume - Remote .............. SKIPPED
[INFO] Apache Log4j Samples: Flume - Embedded ............ SKIPPED
[INFO] Apache Log4j BOM .................................. SKIPPED
[INFO] Apache Log4j NoSQL ................................ SKIPPED
[INFO] Apache Log4J Performance Tests .................... SKIPPED
[INFO] Apache Log4j Streaming Interface .................. SKIPPED
[INFO] Apache Log4j JUL Adapter .......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------


Ralph

> On Nov 29, 2014, at 7:01 AM, Gary Gregory <garydgregory@gmail.com> wrote:
> 
> ah there is more info: http://ci.apache.org/builders/log4j2-nightly/builds/177/steps/compile_1/logs/stdio
<http://ci.apache.org/builders/log4j2-nightly/builds/177/steps/compile_1/logs/stdio>
> 
> Gary
> 
> On Sat, Nov 29, 2014 at 7:18 AM, Gary Gregory <garydgregory@gmail.com <mailto:garydgregory@gmail.com>>
wrote:
> How can we tell what's wrong?
> 
> Gary 
> 
> 
> -------- Original message --------
> From: buildbot@apache.org <mailto:buildbot@apache.org>
> Date:11/29/2014 03:17 (GMT-05:00)
> To: log4j-dev@logging.apache.org <mailto:log4j-dev@logging.apache.org>
> Cc:
> Subject: buildbot exception in ASF Buildbot on log4j2-nightly
> 
> The Buildbot has detected a build exception on builder log4j2-nightly while building
ASF Buildbot. Full details are available at:
>     http://ci.apache.org/builders/log4j2-nightly/builds/177 <http://ci.apache.org/builders/log4j2-nightly/builds/177>
> 
> Buildbot URL: http://ci.apache.org/ <http://ci.apache.org/>
> 
> Buildslave for this Build: lares_ubuntu
> 
> Build Reason: The Nightly scheduler named 'log4j2Nightly' triggered this build
> Build Source Stamp: HEAD
> Blamelist: 
> 
> BUILD FAILED: exception git compile_1
> 
> Sincerely,
> -The Buildbot
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org <mailto:log4j-dev-unsubscribe@logging.apache.org>
> For additional commands, e-mail: log4j-dev-help@logging.apache.org <mailto:log4j-dev-help@logging.apache.org>
> 
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com <mailto:garydgregory@gmail.com> | ggregory@apache.org
 <mailto:ggregory@apache.org>
> Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
> Home: http://garygregory.com/ <http://garygregory.com/>
> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>

Mime
View raw message