carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover
issue:
URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502937529
the Test failure was due to triggering rollover twice within a single
interval of the smallest date component (millisecond) withou
carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover
issue:
URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502797492
@rgoers Tests all pass, I cannot reproduce the failure anymore. Thanks!
--
carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover
issue:
URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502748224
I was able to reproduce this failure on a mac, so I don't think it had to do
with windows. I'll give it a run and check if I can s
carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover
issue:
URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502499969
Ah, ran several more iterations and got a failure with trace enabled:
https://gist.github.com/carterkozak/c6a3bc6cfc258744bb5feb8a
carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover
issue:
URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502499719
You're right, I set the status logger level too early and failed to record
anything while the test was running.
I was not able
carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover
issue:
URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502492251
If I set the status logger level to trace and don't register the listener, I
don't see anything helpful in the log surrounding fai
carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover
issue:
URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502491851
I think we have a subtle race somewhere, when I keep
`statusLogger.registerListener(this);` commented I can reproduce failures, bu
carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover
issue:
URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502475511
@rgoers I've been able to get the test to fail locally with this: #277
That said there could be something odd going on with the
