[
https://issues.apache.org/jira/browse/HBASE-16384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414344#comment-15414344
]
Appy edited comment on HBASE-16384 at 8/9/16 10:25 PM:
-------------------------------------------------------
Sorry for bad urls in example. But in practice, there will always be multiple
urls. One for [post-commit
job|https://builds.apache.org/view/All/job/HBase-Trunk_matrix/], and another
for [flaky-tests runner job|https://builds.apache.org/job/HBase-Flaky-Tests/].
If it was a script handling just single url, we wouldn't be having this
discussion (i would have sent the patch with multiple options in first place).
:)
was (Author: appy):
Sorry for bad urls in example. But in practice, there will always be multiple
urls. One for post-commit, and another for flaky-tests runner.
If it was a script handling just single url, we wouldn't be having this
discussion (i would have sent the patch with multiple options in first place).
:)
> Update report-flakies.py script to allow specifying a list of build ids to be
> excluded
> --------------------------------------------------------------------------------------
>
> Key: HBASE-16384
> URL: https://issues.apache.org/jira/browse/HBASE-16384
> Project: HBase
> Issue Type: Bug
> Reporter: Appy
> Assignee: Appy
> Attachments: HBASE-16384.master.001.patch
>
>
> Sometimes, builds fail mysteriously and leave lots of tests hanging. This
> makes [flaky
> list|https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html]
> go crazy.
> This patch adds that feature to specify build ids to exclude in
> report-flakies.py.
> If we find that a build screwed up, we can exclude it using "exclude=" option
> in --urls param and rerun the job to fix the flaky list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
