You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Gary Gregory <ga...@gmail.com> on 2016/09/15 02:45:04 UTC
Failures in JeroMqAppender tests
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: garydgregory@gmail.com | 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
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: Failures in JeroMqAppender tests
Posted by Gary Gregory <ga...@gmail.com>.
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 <bo...@gmail.com> 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 <ga...@gmail.com>
> 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: garydgregory@gmail.com | 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
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
--
E-Mail: garydgregory@gmail.com | 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
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: Failures in JeroMqAppender tests
Posted by Matt Sicker <bo...@gmail.com>.
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 <ga...@gmail.com> 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: garydgregory@gmail.com | 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
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
--
Matt Sicker <bo...@gmail.com>