[
https://issues.apache.org/jira/browse/HBASE-20387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585342#comment-16585342
]
Sean Busbey commented on HBASE-20387:
-------------------------------------
the dashboard reports all of the runs that it sees for a given test. as I
mentioned before, there being 5 runs from the flaky job was just a matter of
timing; the new flaky job had only run 5 times when the report you linked to
was generated.
looking at the current run:
https://builds.apache.org/job/HBASE-Find-Flaky-Tests/job/master/4/artifact/dashboard.html
you can see the flaky section has up to 40 runs for some of the tests,
including 3 that only have a single failure in those runs.
> flaky infrastructure should work for all branches
> -------------------------------------------------
>
> Key: HBASE-20387
> URL: https://issues.apache.org/jira/browse/HBASE-20387
> Project: HBase
> Issue Type: Improvement
> Components: test
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Critical
> Fix For: 3.0.0, 1.5.0, 1.2.7, 1.3.3, 2.0.2, 2.2.0, 2.1.1, 1.4.7
>
> Attachments: HBASE-20387.0.patch, HBASE-20387.1.patch
>
>
> We need a flaky list per-branch, since what does/does not work reliably on
> master isn't really relevant to our older maintenance release lines.
> We should just make the invocation a step in the current per-branch nightly
> jobs, prior to when we need the list in the stages that run unit tests. We
> can publish it in the nightly job as well so that precommit can still get it.
> (and can fetch it per-branch if needed)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
