[
https://issues.apache.org/jira/browse/HBASE-16384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414351#comment-15414351
]
Dima Spivak commented on HBASE-16384:
-------------------------------------
In that case, how about use {{action='append'}} style arguments for
{{excluded-builds}} and {{max-builds}}, too, in that case and require nulls or
something for cases of URLs we don't want to have excluded builds for? If you
have three lists, they'll be kept synced in that case.
> 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)
