[
https://issues.apache.org/jira/browse/HBASE-20387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580150#comment-16580150
]
Sean Busbey commented on HBASE-20387:
-------------------------------------
I have things up on a branch, waiting to finish running through things but if
folks want to take a peek:
*
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests-per-branch/
*
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Flaky-Tests-per-branch/
*
https://builds.apache.org/blue/organizations/jenkins/HBase%20Nightly/detail/HBASE-20387/
Note that since I'm testing the jobs currently have a different name then
what'll be in the patch. Specifically the jobs I like here with
"FOO-per-branch" names will replace the jobs that are currently named "FOO".
I'll do this by renaming jenkins jobs so that we can still dig up the old info
for a bit if needed.
> 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
>
> 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)
