[
https://issues.apache.org/jira/browse/HBASE-16384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414366#comment-15414366
]
Appy commented on HBASE-16384:
------------------------------
I did consider that case in the starting. So basically it's,
--urls="https://builds.apache.org/job/HBase1/ excludes=10,20 num=5"
--urls="https://builds.apache.org/job/HBase2/ num=10"
--urls="https://builds.apache.org/job/HBase3/ excludes=100,200"
OR
--urls="https://builds.apache.org/job/HBase1/";
--excluded-builds="10,20"
--max-builds=5
--urls="https://builds.apache.org/job/HBase2/";
--excluded-builds="-1" (or NULL, or something else)
--max-builds=10
--urls="https://builds.apache.org/job/HBase1/";
--excluded-builds="100,200"
--max-builds=0 (or -1, means no limit)
In the second one, I don't like the fact that the exact order of CLI arguments
matter.
> 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)
