logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <boa...@gmail.com>
Subject Re: Jenkins build became unstable: Log4j 2.x #1745
Date Tue, 01 Mar 2016 20:22:37 GMT
Looks like I found it. There was no "T" converter key specified (just
threadId and tid). Added back to the converter, should probably fix the
test based on local testing.

On 1 March 2016 at 14:12, Matt Sicker <boards@gmail.com> wrote:

> This one looks real. Has to do with the recently-added thread ID pattern
> converter.
>
> On 1 March 2016 at 14:02, Apache Jenkins Server <jenkins@builds.apache.org
> > wrote:
>
>> See <https://builds.apache.org/job/Log4j%202.x/1745/changes>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>>
>
>
> --
> Matt Sicker <boards@gmail.com>
>



-- 
Matt Sicker <boards@gmail.com>

Mime
View raw message