Dawid: I was also wondering why this exception still passed the test, that's kind of disturbing actually, and it's nice to know I'm not hallucinating.
As to _why_ it tries to write to test dir, it seems to be related to SOLR-4575. That issue is I wasn't populating each core descriptor with keys like solr.core.name, solr.core.dataDir, solr.core.instanceDir and the associated values. These were _always_ populated until SOLR-4196. Perhaps Uwe's comment about other tests changing the environment is pertinent. At any rate, when I fixed 4575, Presto! I could run the individual test. With tests.iters=1000. no exceptions at all. So the problem may disappear next time you update. I can give you the magic for making local changes to make the problem come back if you want to be able to see it happen to track down why tests succeed anyway, trivial edits to two files..... Thanks for looking at this, tracking back through all the test setup gives me a headache.... Erick On Wed, Mar 13, 2013 at 6:08 PM, Dawid Weiss <[email protected]>wrote: > 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] > >
