[ 
https://issues.apache.org/jira/browse/SOLR-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912930#comment-13912930
 ] 

Robert Muir commented on SOLR-5775:
-----------------------------------

I would actually like to enable solr tests for the smoketester as well. I think 
its really bad this is disabled, as there could be a bad problem in a release 
candidate and only manual verification really finds it. Lots of people 
smoketest on different machines and platforms and I think this has value.

I know this all sounds like a high bar, but I think if we stay on top of this, 
it will make it much easier on everyone. In this case it really is just a few 
bad apples to fix!


> Disable constantly failing solr tests
> -------------------------------------
>
>                 Key: SOLR-5775
>                 URL: https://issues.apache.org/jira/browse/SOLR-5775
>             Project: Solr
>          Issue Type: Bug
>          Components: Build
>            Reporter: Robert Muir
>
> Currently, solr tests are failing 90%+ of the time. We've been through this 
> before many times, the argument is always that someone is looking at the 
> failures and knows which ones are bad.
> This argument is a lie. Nobody is watching these failures, or 
> DistributedQueryComponentOptimizationTest would not have failed repeatedly 
> for two straight days when the fix was trivial (I fixed this last night: 
> http://svn.apache.org/r1571930)
> Its frustrating to me as a committer, solr tests *NEVER* pass on my machine, 
> no matter how many times I try. How can i possibly commit something without 
> knowing i am making the situation even worse?
> This is all a big problem for developers, release managers, even users of the 
> project. The test suite should pass.
> The old argument that "solr tests are allowed to fail" is no longer valid. I 
> will disable all constantly failing tests.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to