I get value from this test - if it was disabled, I'd probably re-enable it. would be great if it didn't fail so much, but the type of fail tells me something. I work on improving tests all the time - I also need to fit in a life and further dev. Getting large scale integration tests to pass reliably on so many different systems is hard! Lucene tests are easy in comparison. I'd rather have a test that tells me something based on the fail than no coverage.
If someone doesn't want to help improve the test, fine - doesn't mean it should be disabled. It passes 100% of the time on my machine. I've worked on both Lucene and solr tests. Due to the nature of each, it's easy to make solid Lucene tests and hard to make solid solr tests in many cases. Boo hoo. Library vs large application with many integration tests. On Sunday, September 16, 2012, Robert Muir wrote: > On Sun, Sep 16, 2012 at 10:02 PM, Yonik Seeley > <[email protected]<javascript:;>> > wrote: > > On Sun, Sep 16, 2012 at 9:53 PM, Robert Muir > > <[email protected]<javascript:;>> > wrote: > >> I dont care about replication > > > > Yeah, I know. That's the crux of some of the biggest problems here. > > Really? Its somehow my responsibility to fix this test and my fault > that its broken? > > I think you have seriously lost your mind. > > -- > lucidworks.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] <javascript:;> > For additional commands, e-mail: [email protected] <javascript:;> > > -- - Mark
