I've filed LOG4J2-2613 to track the fix. -ck
https://issues.apache.org/jira/browse/LOG4J2-2613 On Thu, May 23, 2019, at 09:48, Matt Sicker wrote: > I’m normally OK with that sort of thing provided it’s fixed before a > release. > > On Thu, May 23, 2019 at 06:23, Carter Kozak <cko...@ckozak.net> wrote: > > > Do you mind if I temporarily ignore this test on the master branch to > > allow other builds to succeed? If that's alright with you, I'll file an > > issue so we can track fixing and re-enabling the test. > > > > -ck > > > > On Tue, May 14, 2019, at 10:40, Ralph Goers wrote: > > > I made the change so I will take a look when I can. > > > > > > Ralph > > > > > > > On May 14, 2019, at 7:21 AM, Carter Kozak <cko...@ckozak.net> wrote: > > > > > > > > It looks like github builds on master have been broken since > > 619707edd57fd6f562ea154d1eac56708b6634e2 > > > > > > > > LOG4J2-2602 - Update file time when size based triggering policy is > > used without a time-based triggering policy > > > > > > > > Failing with: > > > > [ERROR] Failures: > > > > [ERROR] RollingAppenderSizeWithTimeTest.testAppender:95 Log messages > > lost : <number> > > > > I don't see a similar failure on builds.apache.org, so it may be a > > race or timezone problem. > > > > > > > > I may be able to take a look over the weekend if nobody else is > > tracking > > > > -ck > > > > > > > > > > > > > > > > -- > Matt Sicker <boa...@gmail.com> >
