OK, I set the status logger to "all" for this one test class. Let's see what happens...
Gary On Wed, Sep 14, 2016 at 9:34 PM, Matt Sicker <[email protected]> wrote: > An Appender can be null if there's an error during the building of the > plugin. There would most likely be an exception thrown somewhere which > should be logged at the status="error" level, but it might not be if it's > not apparent in the test output. I guess try status="debug" on that test? > > On 14 September 2016 at 21:45, Gary Gregory <[email protected]> > wrote: > >> We seem to get random failures in JeroMqAppender tests, for example: >> >> https://builds.apache.org/job/Log4j%202.x/2314/testReport/ >> >> How can the Appender be null? >> >> Gary >> >> -- >> E-Mail: [email protected] | [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 >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >> > > > > -- > Matt Sicker <[email protected]> > -- E-Mail: [email protected] | [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 Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
