On Fri, Mar 19, 2021 at 5:12 PM Chris Hostetter <[email protected]> wrote:
> > : I did have to tweak the "reproduce with:" line to reproduce it though... > : maybe because it was a timeout? > : > : It said: --tests > : "org.apache.lucene.index.TestDocumentsWriterStallControl.classMethod" > : But it should be: --tests > : > "org.apache.lucene.index.TestDocumentsWriterStallControl.testAcquireReleaseRace" > : ? > : Or maybe no test method at all since we don't know who is truly to blame? > > There are two failures reported, w/two reproduce lines in the output. One > is testAcquireReleaseRace, the other is 'classMethod' -- IIUC classMethod > is the generic way the gradle test runner reports that something failed at > the suite (or static class init?) level ... like an AfterClass method, or > as Dawid said: a suite timeout (which i think is inforced via a ClassRule? > ... not sure ...) > > I think that in the case of a suite timeout you'll always see that test + > 'classMethod' failure pattern -- unless the test finishes in a timely > manner and it's some AfterClass cleanup that "hangs" > > > In this case, the test class has 3 methods and no before/afterclass/setup/teardown. So I think it is either that acquireReleaseRace provokes a deadlock, or it is a problem in test-framework. But you are correct, there are two "reproduce with"'s (class and test level), and i just lazily grabbed one of them, it happened to be the class level one. But IMO it should still work, instead of "classMethod", just make the "reproduce with" print no method at all. it should just run all 3 test methods in this case?
