Jenkins appears to be invoking maven to allow failed unit tests not to fail the 
build. If you look through each of the module summaries you will probably find 
a failure.

Ralph

> On Dec 29, 2015, at 7:12 PM, Gary Gregory <[email protected]> wrote:
> 
> Hm, how can the build be unstable when we have:
> 
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Log4j 2 .................................... SUCCESS [  9.465 s]
> [INFO] Apache Log4j API .................................. SUCCESS [ 14.740 s]
> [INFO] Apache Log4j Core ................................. SUCCESS [07:50 min]
> [INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [ 11.411 s]
> [INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [  6.353 s]
> [INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [  3.848 s]
> [INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [  3.797 s]
> [INFO] Apache Log4j Flume Bridge ......................... SUCCESS [ 24.535 s]
> [INFO] Apache Log4j Web .................................. SUCCESS [  5.105 s]
> [INFO] Apache Log4j Tag Library .......................... SUCCESS [ 12.618 s]
> [INFO] Apache Log4j JMX GUI .............................. SUCCESS [  2.503 s]
> [INFO] Apache Log4j Samples .............................. SUCCESS [  0.600 s]
> [INFO] Apache Log4j Samples: Flume - Common .............. SUCCESS [  3.075 s]
> [INFO] Apache Log4j Samples: Flume - Remote .............. SUCCESS [  3.102 s]
> [INFO] Apache Log4j Samples: Flume - Embedded ............ SUCCESS [  4.763 s]
> [INFO] Apache Log4j Samples: Configuration ............... SUCCESS [  4.797 s]
> [INFO] Apache Log4j Samples: LoggerProperties ............ SUCCESS [  4.484 s]
> [INFO] Apache Log4j BOM .................................. SUCCESS [  0.568 s]
> [INFO] Apache Log4j NoSQL ................................ SUCCESS [  5.236 s]
> [INFO] Apache Log4J Performance Tests .................... SUCCESS [ 20.396 s]
> [INFO] Apache Log4j Streaming Interface .................. SUCCESS [  6.848 s]
> [INFO] Apache Log4j JUL Adapter .......................... SUCCESS [  7.201 s]
> [INFO] Apache Log4j Liquibase Binding .................... SUCCESS [  4.124 s]
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 10:51 min
> [INFO] Finished at: 2015-12-30T01:51:54+00:00
> [INFO] Final Memory: 52M/749M
> [INFO] 
> ------------------------------------------------------------------------
> ?
> Gary
> ---------- Forwarded message ----------
> From: Apache Jenkins Server <[email protected] 
> <mailto:[email protected]>>
> Date: Tue, Dec 29, 2015 at 5:52 PM
> Subject: Jenkins build became unstable: Log4j 2.x #1608
> To: [email protected] <mailto:[email protected]>
> 
> 
> See <https://builds.apache.org/job/Log4j%202.x/1608/changes 
> <https://builds.apache.org/job/Log4j%202.x/1608/changes>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] 
> <mailto:[email protected]>
> For additional commands, e-mail: [email protected] 
> <mailto:[email protected]>
> 
> 
> 
> 
> -- 
> E-Mail: [email protected] <mailto:[email protected]> | 
> [email protected]  <mailto:[email protected]>
> 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>

Reply via email to