lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomás Fernández Löbbe (JIRA) <>
Subject [jira] [Commented] (SOLR-10032) Create report to assess Solr test quality at a commit point.
Date Fri, 10 Feb 2017 18:05:41 GMT


Tomás Fernández Löbbe commented on SOLR-10032:

Interesting that PeerSyncReplicationTest is rock-solid for you, It fails quite often to me
(and seems like also in Jenkins)

> 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: Lucene-Solr Master Test Beast Results 01-24-2017-9899cbd031dc3fc37a384b1f9e2b379e90a9a3a6
Level Medium- Running 30 iterations, 12 at a time .pdf, Lucene-Solr Master Test Beasults 02-01-2017-bbc455de195c83d9f807980b510fa46018f33b1b
Level Medium- Running 30 iterations, 10 at a time.pdf, Lucene-Solr Master Test Beasults 02-08-2017-6696eafaae18948c2891ce758c7a2ec09873dab8
Level Medium+- Running 30 iterations, 10 at a time, 8 cores.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.
> Reports:
> 01/24/2017 -
> 02/01/2017 -
> 02/08/2017 -

This message was sent by Atlassian JIRA

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

View raw message