Re: Jenkins build is unstable: Log4j 2.x #2019

2016-06-12 Thread Ralph Goers
Oh, but yes, if the first file is non-zero and the second file is zero then it should fail - and that would be a correct failure. Ralph > On Jun 12, 2016, at 12:38 AM, Ralph Goers wrote: > > Both files write a header, 100 events and a footer. Neither should be zero

Re: Jenkins build is unstable: Log4j 2.x #2019

2016-06-12 Thread Ralph Goers
Both files write a header, 100 events and a footer. Neither should be zero and both should be the same length. Ralph > On Jun 11, 2016, at 11:44 PM, Remko Popma wrote: > > If the first file on the stream is non-zero length, and the second file is > zero length, then

Re: Jenkins build is unstable: Log4j 2.x #2019

2016-06-12 Thread Remko Popma
If the first file on the stream is non-zero length, and the second file is zero length, then won't the test fail? On Sun, Jun 12, 2016 at 2:45 PM, Ralph Goers wrote: > Looked at the test again. It had some bugs in it. > > Ralph > > On Jun 11, 2016, at 10:22 PM, Ralph

Re: Jenkins build is unstable: Log4j 2.x #2019

2016-06-11 Thread Ralph Goers
Looked at the test again. It had some bugs in it. Ralph > On Jun 11, 2016, at 10:22 PM, Ralph Goers wrote: > > Yes. It creates the file and writes to it. The test should then end and run > again. On the second run the file should roll over. The files should both >

Re: Jenkins build is unstable: Log4j 2.x #2019

2016-06-11 Thread Ralph Goers
Yes. It creates the file and writes to it. The test should then end and run again. On the second run the file should roll over. The files should both have the header, footer, and same number of lines so they should be the same size. Ralph > On Jun 11, 2016, at 10:08 PM, Remko Popma

Re: Jenkins build is unstable: Log4j 2.x #2019

2016-06-11 Thread Remko Popma
Hm... this is the second time I see this test fail: Stacktrace java.lang.AssertionError at org.apache.logging.log4j.core.appender.rolling.RollingAppenderOnStartupTest.afterClass(RollingAppenderOnStartupTest.java:85) What does this test do? It looks like it remembers the size of the

Jenkins build is unstable: Log4j 2.x #2019

2016-06-11 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org