lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ishan Chattopadhyaya (JIRA)" <>
Subject [jira] [Commented] (SOLR-10032) Create report to assess Solr test quality at a commit point.
Date Wed, 25 Jan 2017 20:01:26 GMT


Ishan Chattopadhyaya commented on SOLR-10032:

I think a hammer approach (and probably effective) for now would be disable all flaky tests.
While someone should anyway need to work on them, their getting resolved would not get in
the way of a regular developer now trying to figure out the basic questions Mark mentioned.

> Create report to assess Solr test quality at a commit point.
> ------------------------------------------------------------
>                 Key: SOLR-10032
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message