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

Mark Miller commented on SOLR-10032:
------------------------------------

bq. If there's stuff we can do to raise the visibility of such tests,

I'm hoping having this report with all the tests compared will help give us 
backing to do just this. Right now, it's hard to be objective about which tests 
are the problem and how hard you should push back on a flakey test. Fails for 
you, not for me, fails on jenkins but so do many others, etc.

With this report and the logs of all 30 runs for each test, I think it will be 
much easier to create high priority JIRA issues for bad tests and pressure 
contributors to improve them. We can also send an occasional email to the dev 
list and highlight problem tests.

Open to other ideas as well of course.

> Create report to assess Solr test quality at a commit point.
> ------------------------------------------------------------
>
>                 Key: SOLR-10032
>                 URL: https://issues.apache.org/jira/browse/SOLR-10032
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Tests
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>         Attachments: Test-Report-Sample.pdf
>
>
> We have many Jenkins instances blasting tests, some official, some policeman, 
> I and others have or had their own, and the email trail proves the power of 
> the Jenkins cluster to find test fails.
> However, I still have a very hard time with some basic questions:
> what tests are flakey right now? which test fails actually affect devs most? 
> did I break it? was that test already flakey? is that test still flakey? what 
> are our worst tests right now? is that test getting better or worse?
> We really need a way to see exactly what tests are the problem, not because 
> of OS or environmental issues, but more basic test quality issues. Which 
> tests are flakey and how flakey are they at any point in time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to