See my other post. Ist a deadlock or like that, this is why it affects some machines. Sometimes with that commit it also passes in 8 seconds, but on my machine it hangs in a loop for hours (80% of all tries).
With this commit reverted it runs every time in 8 seconds - constantly. ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Chris Hostetter [mailto:[email protected]] > Sent: Friday, August 19, 2011 12:21 AM > To: [email protected] > Subject: Re: Solr Tests in trunk SLOOOOOOOOOOOOOOOOOOOOOOOOOOW > > > : I'm quoting you here: SolrExampleJettyTest.testUnicode - 2 hr 50 > : min of 3 hr 43 min total > : > : I did subtraction... so the other test methods in this single class > : are doing *something* for nearly an hour here. > > i don't disagree with you ... i just didn't understand your "9 + 47 + 53" > comment. > > Like i said: something, somewhere, is huting these example tests (on > *some* hardware), and it just happens to be hurting testUnicode the worst .... i > suspect it may just be because testUnicode does random looping so any > overhead on an action in that test (connecting to the server, deleting all, adding > docs, commiting, etc...) would be a lot more pronounced and noticable. > > but what really confuses me is why only some subclasses (like > SolrExampleEmbeddedTest) see these really long times, and others (like > SolrExampleStreamingTest) don't ... a test that streams the data over HTTP > takes 1.5 minutes, but the same test using an embedded method call to do the > same actions takes 2.5 hours? WTF?!?! > > -Hoss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
