lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dawid Weiss <>
Subject Re: [JENKINS] Lucene-Solr-trunk-Windows (64bit/jdk1.7.0_07) - Build # 673 - Failure!
Date Sat, 08 Sep 2012 12:51:04 GMT
> 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
[junit4:junit4]    > 	at java.lang.Thread.getStackTrace(
[junit4:junit4]    > 	at
[junit4:junit4]    > 	at
[junit4:junit4]    > 	at
[junit4:junit4]    > 	at

tells you it was registered in TestMultiMMap.testSeekSliceEnd (line
164) and on close threw:

Caused by: Could not remove:
[junit4:junit4]    > 	at


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message