Good catch, thanks! -Yonik On Sat, Aug 1, 2015 at 10:26 PM, Shalin Shekhar Mangar <[email protected]> wrote: > I committed a fix to the CdcrUpdateLogTest to reset the test hooks. > > On Sun, Aug 2, 2015 at 10:42 AM, Shalin Shekhar Mangar > <[email protected]> wrote: >> Yeah, looks like the Cdcr tests is enabling the test hooks in a static >> context and not cleaning up? The TestStressRecovery ends up calling >> the tests hook at CdcrUpdateLogTest.java line 444. Look at the failure >> stack trace: >> >> [junit4] 2> NOTE: reproduce with: ant test >> -Dtestcase=TestStressRecovery -Dtests.method=testStressRecovery >> -Dtests.seed=301358D17C79C090 -Dtests.multiplier=3 -Dtests.slow=true >> -Dtests.locale=lt -Dtests.timezone=America/Havana -Dtests.asserts=true >> -Dtests.file.encoding=UTF-8 >> [junit4] ERROR 92.3s J2 | TestStressRecovery.testStressRecovery <<< >> [junit4] > Throwable #1: >> java.util.concurrent.ExecutionException: java.lang.AssertionError >> [junit4] > at >> __randomizedtesting.SeedInfo.seed([301358D17C79C090:8A29318CE3917F9E]:0) >> [junit4] > at >> java.util.concurrent.FutureTask.report(FutureTask.java:122) >> [junit4] > at java.util.concurrent.FutureTask.get(FutureTask.java:206) >> [junit4] > at >> org.apache.solr.search.TestStressRecovery.testStressRecovery(TestStressRecovery.java:370) >> [junit4] > at java.lang.Thread.run(Thread.java:745) >> [junit4] > Caused by: java.lang.AssertionError >> [junit4] > at >> org.apache.solr.update.CdcrUpdateLogTest$1.run(CdcrUpdateLogTest.java:444) >> [junit4] > at >> org.apache.solr.update.UpdateLog$LogReplayer.doReplay(UpdateLog.java:1320) >> [junit4] > at >> org.apache.solr.update.UpdateLog$LogReplayer.run(UpdateLog.java:1258) >> [junit4] > at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >> [junit4] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> [junit4] > at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >> >> On Sun, Aug 2, 2015 at 10:22 AM, Yonik Seeley <[email protected]> wrote: >>> It's been two years since this test has failed, and it seems to have >>> failed multiple times recently. The test itself hasn't changed. >>> Anyone have any ideas what has changed here? >>> >>> Hmmm, looking at the output, perhaps this is this just bleed-over from >>> other failing tests? >>> >>> -Yonik >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> >> -- >> Regards, >> Shalin Shekhar Mangar. > > > > -- > Regards, > Shalin Shekhar Mangar. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
