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 <[email protected]> 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 <[email protected]> > wrote: > > Hi All: > > > > It looks like the latest commit causes the build to fail in > > the log4j-1.2-api module. > > > > Gary > -- Matt Sicker <[email protected]>
