: I think this one is just another opportunity for improvement... this test : fails often for me, and it looked like it also failed for solr trunk last : night too (except it was testSimple)
This doesn't seem like the usual "couldn't connect to the master because of timing issues" type problem, notice the error log... : > > [junit] SEVERE: Master at: http://localhost:TEST_PORT/solr/replication : > is not available. Index fetch failed. Exception: Invalid uri : > 'http://localhost:TEST_PORT/solr/replication': invalid port number ...I'm pretty sure something in the test setup is suppose to search/replace in a slave config file to refrence the dynamicly created master port, no idea why that wouldn't have happened. I can't reproduce it ... but it definitely seems weirder then normal. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
