On 12/12/2012 7:43 AM, Mark Miller wrote:
Well, I guess normal depends on who you are - for my machine it's closer to 2
minutes. If it's 4 minutes for a lot of people, it may make sense to break it
into 2 sets.
Right now these tests are catching a problem around replication and shutdown
like I mentioned. The replication test hits the same thing sometimes, but much
less often.
If you don't use replication, you are right - this probably has no effect on
you. But they are not SolrCloud specific fails.
I don't use replication or SolrCloud. If SolrCloud can eventually
support the way that I divide up my shards and cores (lazily watching
SOLR-2592), I may one day move to using two separate cloud
installations. I've found a lot of value in updating both copies of my
index independently, so I don't foresee using replication until our
query volume requires additional servers.
Because these failures are caused by real problems and aren't from buggy
tests, I'll stop complaining about failures now. I'd like to have the
tests run faster, but if that's not possible, it's not possible. I
really like what you're saying on SOLR-4169, btw. The idea of separating
unit tests and integration tests is intriguing. For the kind of quick
simple changes that I make myself, I could skip the integration tests,
but do them when I 'svn up' and before deploying to production.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
