I took a quick look and my first question would be *why this test even
passes* if it throws exceptions internally and clearly cannot clean up
after itself:

[junit4:junit4]   2> !!!! WARNING: best effort to remove
c:\Work\lucene\trunk\solr\build\solr-solrj\test\J0\.\solrtest-TestSolrProperties-1363211585047\data1\tlog\tlog.0000000000000000000
FAILED !!!!!
[junit4:junit4]   2> !!!! WARNING: best effort to remove
c:\Work\lucene\trunk\solr\build\solr-solrj\test\J0\.\solrtest-TestSolrProperties-1363211585047\data1\tlog
FAILED !!!!!
[junit4:junit4]   2> !!!! WARNING: best effort to remove
c:\Work\lucene\trunk\solr\build\solr-solrj\test\J0\.\solrtest-TestSolrProperties-1363211585047\data1
FAILED !!!!!
[junit4:junit4]   2> 6033 T11
oascse.AbstractEmbeddedSolrServerTestCase.tearDown WARNING !!!!
WARNING: best effort to remove
c:\Work\lucene\trunk\solr\build\solr-solrj\test\J0\.\solrtest-TestSolrProperties-1363211585047\data
FAILED !!!!!

This is odd and this is in fact the source of all the confusion (I think).

I can reproduce this issue you mentioned without a problem. Indeed, it
tries to mkdir in a directory it has no access to, throws an exception
but does *not* fail the test. So when you run:

ant -Dtestcase=TestSolrProperties test

you see the test's output on the console because passing -Dtestcase
automatically enables output pumping to the console. When you run:

ant test

this test *also* throws an exception, it is an identical behavior. The
problem is that this test passes and when not limited to a single test
case, the output from tests that pass is hidden. You can still see it
in:

cat trunk/solr/build/solr-solrj/test/tests-report.txt

and sure enough it contains exactly the same exception. Hope this
helps a bit although I still have no idea how to fix the core of the
problem (or two cores -- one why this test even passes, the second why
it tries to write to src dir).

Dawid

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to