The test may be too strict: it currently asserts that rollover is done within 50 millisecs and fails if that's not the case. Changing 50 to 500 (line 140) should avoid the false positives while keeping the test valid.
Sent from my iPhone > On 2014/01/20, at 16:21, Ralph Goers <[email protected]> wrote: > > I ran the test by itself and then ran the full build a couple of times and it > passed. There must be a timing problem in the test. > > Ralph > >> On Jan 19, 2014, at 8:03 PM, Ralph Goers <[email protected]> wrote: >> >> ------------------------------------------------------------------------------- >> Test set: >> org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManagerTest >> ------------------------------------------------------------------------------- >> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.414 sec >> <<< FAILURE! - in >> org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManagerTest >> testFileTimeBasedOnSystemClockWhenAppendIsFalse(org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManagerTest) >> Time elapsed: 0.908 sec <<< FAILURE! >> java.lang.AssertionError: null >> at org.junit.Assert.fail(Assert.java:86) >> at org.junit.Assert.assertTrue(Assert.java:41) >> at org.junit.Assert.assertTrue(Assert.java:52) >> at >> org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManagerTest.testFileTimeBasedOnSystemClockWhenAppendIsFalse(RollingRandomAccessFileManagerTest.java:150) >
