[
https://issues.apache.org/jira/browse/HBASE-20387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583345#comment-16583345
]
Hudson commented on HBASE-20387:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #452 (See
[https://builds.apache.org/job/HBase-1.3-IT/452/])
HBASE-20387 turn flaky test tracking infra into per-branch pipeline. (busbey:
rev 0c0c723e2559211fff73f9f876e2a582a60680a8)
* (edit) dev-support/Jenkinsfile
* (add) dev-support/flaky-tests/report-flakies.py
* (add) dev-support/flaky-tests/flaky-reporting.Jenkinsfile
* (add) dev-support/flaky-tests/findHangingTests.py
* (edit) dev-support/hbase_nightly_yetus.sh
* (delete) dev-support/findHangingTests.py
* (add) dev-support/flaky-tests/run-flaky-tests.Jenkinsfile
* (add) dev-support/Dockerfile
* (add) dev-support/flaky-tests/flaky-dashboard-template.html
> 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
> 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)
