I agree, these events do feel coincidental. Not sure what constitutes the "example test framework", but I did move the ExternalPaths utility class into the solr test-framework, because it's used from both the Solr core tests and the Solrj tests, which don't depend (anymore) on the Solr core tests. (branch_3x:7/13/2011:r1146191)
I also had to change ExternalPaths.determineSourceHome() to handle the situation where there is no solr/conf/ dir in the classpath, e.g. the situation for Solrj & common tests (which are now housed with the Solrj internal module) -- these tests do not have solr/core/src/test-files/solr/conf/ in their classpath. (branch_3x:7/22/2011:r1149691) That all said, it's not clear to me how these changes could have affected directory creation? Steve > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Yonik > Seeley > Sent: Monday, August 01, 2011 11:49 AM > To: [email protected] > Subject: Re: [JENKINS] Lucene-Solr-tests-only-3.x - Build # 9905 - > Failure > > Caused by: java.io.IOException: Cannot create directory: > /usr/home/hudson/hudson-slave/workspace/Lucene-Solr-tests-only- > 3.x/checkout/solr/example/multicore/core1/data/index > at > org.apache.lucene.store.SimpleFSLock.obtain(SimpleFSLockFactory.java:121) > at org.apache.lucene.store.Lock.obtain(Lock.java:72) > at > org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1116) > > > It feels like we've been experiencing a lot of failures lately in the > "example" jetty tests. > Although it may be a coincidence, it feels like it coincided with the > solr build rewrite (and IIRC there were some changes made to the > example test framework at that time?) > > -Yonik > http://www.lucidimagination.com > > > > On Mon, Aug 1, 2011 at 12:24 AM, Apache Jenkins Server > <[email protected]> wrote: > > https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/9905/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected]
