> I don’t understand the stack trace, so I have no idea. Test looks OK.
There is an infrastructural support for adding "close resource after all the hooks and everything" thingies. It's called closeAfterTest and closeAfterSuite (methods on LuceneTestCase). This was meant to be an easy facility to close/ remove resources; much like a finally but for tests and suites. If such a resource throws an exception on close the stack trace tells you why it failed to close but also where it was "registered" for closing which should help you find out the code fragment that was responsible for the resource. So: [junit4:junit4] > Throwable #1: com.carrotsearch.randomizedtesting.ResourceDisposalError: Resource in scope SUITE failed to close. Resource was registered from thread Thread[id=695, name=TEST-TestMultiMMap.testSeekSliceEnd-seed#[AA4F04524D760878], state=RUNNABLE, group=TGRP-TestMultiMMap], registration stack trace below. [junit4:junit4] > at java.lang.Thread.getStackTrace(Thread.java:1567) [junit4:junit4] > at com.carrotsearch.randomizedtesting.RandomizedContext.closeAtEnd(RandomizedContext.java:150) [junit4:junit4] > at org.apache.lucene.util.LuceneTestCase.closeAfterSuite(LuceneTestCase.java:485) [junit4:junit4] > at org.apache.lucene.util._TestUtil.getTempDir(_TestUtil.java:97) [junit4:junit4] > at org.apache.lucene.store.TestMultiMMap.testSeekSliceEnd(TestMultiMMap.java:164) tells you it was registered in TestMultiMMap.testSeekSliceEnd (line 164) and on close threw: Caused by: java.io.IOException: Could not remove: C:\Jenkins\workspace\Lucene-Solr-trunk-Windows\lucene\build\core\test\J0\.\testSeekSliceEnd4659546750tmp [junit4:junit4] > at org.apache.lucene.util.CloseableFile.close(CloseableFile.java:47) ... Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
