Perhaps we need some kind of stress test here... this kind of failure gives me the willies of seeing it in a production deployment.
Gary On Jun 1, 2017 11:32 AM, "Matt Sicker" <[email protected]> wrote: > I'm pretty sure I've seen that same issue randomly before as well. > > On 1 June 2017 at 12:44, Ralph Goers <[email protected]> wrote: > > > I’ve seen that occasionally I think. No idea what it is about. > > > > Ralph > > > > > On Jun 1, 2017, at 9:42 AM, Gary Gregory <[email protected]> > wrote: > > > > > > Hi All: > > > > > > I've just had this random failure: > > > > > > [INFO] Results: > > > [INFO] > > > [ERROR] Failures: > > > [ERROR] > > > AsyncLoggerThreadContextGarbageFreeTest>AbstractAsyncThreadContextTest > > Base.testAsyncLogWritesToLog:162->AbstractAsyncThreadContextTest > > Base.checkResult:185 > > > AsyncLoggerAndAsyncAppenderTest.log: line 0 > > expected:<...syncLoggerContext > > > i=[0]> but was:<...syncLoggerContext i=[128]> > > > [INFO] > > > [ERROR] Tests run: 1873, Failures: 1, Errors: 0, Skipped: 19 > > > > > > Any thoughts? > > > > > > I was using: > > > > > > Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; > > > 2017-04-03T12:39:06-07:00) > > > Maven home: C:\Java\apache-maven-3.5.0\bin\.. > > > Java version: 1.8.0_131, vendor: Oracle Corporation > > > Java home: C:\Program Files\Java\jdk1.8.0_131\jre > > > Default locale: en_US, platform encoding: Cp1252 > > > OS name: "windows 10", version: "10.0", arch: "amd64", family: > "windows" > > > > > > Gary > > > > > > > > > -- > Matt Sicker <[email protected]> >
