folks, I got more active working on IndexWriter and Soft-Deletes etc. in the last couple of weeks. It's a blast again and I really enjoy it. The one thing that is IMO not acceptable is the status of solr tests. I tried so many times to get them passing on several different OSs but it seems this is pretty hopepless. It's get's even worse the Lucene/Solr QA job literally marks every ticket I attach a patch to as `-1` because of arbitrary solr tests, here is an example:
|| Reason || Tests || | Failed junit tests | solr.rest.TestManagedResourceStorage | | | solr.cloud.autoscaling.SearchRateTriggerIntegrationTest | | | solr.cloud.autoscaling.ScheduledMaintenanceTriggerTest | | | solr.client.solrj.impl.CloudSolrClientTest | | | solr.common.util.TestJsonRecordReader | Speaking to other committers I hear we should just disable this job. Sorry, WTF? These tests seem to fail all the time, randomly and over and over again. This renders the test as entirely useless to me. I even invest time (wrong, I invested) looking into it if they are caused by me or if I can do something about it. Yet, someone could call me out for being responsible for them as a commiter, yes I am hence this email. I don't think I am obliged to fix them. These projects have 50+ committers and having a shared codebase doesn't mean everybody has to take care of everything. I think we are at the point where if I work on Lucene I won't run solr tests at all otherwise there won't be any progress. On the other hand solr tests never pass I wonder if the solr code-base gets changes nevertheless? That is again a terrible situation. I spoke to varun and anshum during buzzwords if they can give me some hints what I am doing wrong but it seems like the way it is. I feel terrible pushing stuff to our repo still seeing our tests fail. I get ~15 build failures from solr tests a day I am not the only one that has mail filters to archive them if there isn't a lucene tests in the failures. This is a terrible state folks, how do we fix it? It's the lucene land that get much love on the testing end but that also requires more work on it, I expect solr to do the same. That at the same time requires stop pushing new stuff until the situation is under control. The effort of marking stuff as bad apples isn't the answer, this requires effort from the drivers behind this project. simon --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
