You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Gary Gregory <ga...@gmail.com> on 2018/05/31 20:38:26 UTC
[log4j] master unit failures
Hi All:
It looks like the latest commit causes the build to fail in
the log4j-1.2-api module.
Gary
Re: [log4j] master unit failures
Posted by Carter Kozak <ck...@apache.org>.
This flake is fixed by
https://github.com/apache/logging-log4j2/commit/40d9b504a9cc2593a19ab9c487eb5c873937ca75
-ck
On Fri, Jun 1, 2018 at 11:59 AM, Matt Sicker <bo...@gmail.com> wrote:
> I've been seeing exceptions related to key stores in the build logs for a
> long time. I always figured it was a test that was testing a failure
> scenario that couldn't quiet the exception logs. Wonder if it's related?
>
> On 31 May 2018 at 17:45, Carter Kozak <c4...@gmail.com> wrote:
>
>> That looks like a recurring flake we've had for at least a couple
>> months months: https://travis-ci.org/apache/logging-log4j2/builds/
>> 365329034
>> Prior to that commit most builds failed before running tests, so I
>> wasn't able to check for the issue earlier.
>>
>> Unfortunately I'm unable to reproduce this failure locally.
>>
>> -ck
>>
>> On Thu, May 31, 2018 at 4:38 PM, Gary Gregory <ga...@gmail.com>
>> wrote:
>> > Hi All:
>> >
>> > It looks like the latest commit causes the build to fail in
>> > the log4j-1.2-api module.
>> >
>> > Gary
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: [log4j] master unit failures
Posted by Matt Sicker <bo...@gmail.com>.
I've been seeing exceptions related to key stores in the build logs for a
long time. I always figured it was a test that was testing a failure
scenario that couldn't quiet the exception logs. Wonder if it's related?
On 31 May 2018 at 17:45, Carter Kozak <c4...@gmail.com> wrote:
> That looks like a recurring flake we've had for at least a couple
> months months: https://travis-ci.org/apache/logging-log4j2/builds/
> 365329034
> Prior to that commit most builds failed before running tests, so I
> wasn't able to check for the issue earlier.
>
> Unfortunately I'm unable to reproduce this failure locally.
>
> -ck
>
> On Thu, May 31, 2018 at 4:38 PM, Gary Gregory <ga...@gmail.com>
> wrote:
> > Hi All:
> >
> > It looks like the latest commit causes the build to fail in
> > the log4j-1.2-api module.
> >
> > Gary
>
--
Matt Sicker <bo...@gmail.com>
Re: [log4j] master unit failures
Posted by Carter Kozak <c4...@gmail.com>.
That looks like a recurring flake we've had for at least a couple
months months: https://travis-ci.org/apache/logging-log4j2/builds/365329034
Prior to that commit most builds failed before running tests, so I
wasn't able to check for the issue earlier.
Unfortunately I'm unable to reproduce this failure locally.
-ck
On Thu, May 31, 2018 at 4:38 PM, Gary Gregory <ga...@gmail.com> wrote:
> Hi All:
>
> It looks like the latest commit causes the build to fail in
> the log4j-1.2-api module.
>
> Gary