[
https://issues.apache.org/jira/browse/HBASE-16384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414316#comment-15414316
]
Appy commented on HBASE-16384:
------------------------------
I know it's weird, but splitting into multiple options seemed more messy to me.
The input is basically tuples where some values maybe missing. for eg{A, [B],
[C]}
If i split into multiple options (where each option correspond to single type
of value, i.e. option for list of A's , B's and C's), syncing up order of
values seems worse to me. Then there can be missing values.
After all the consideration, i went with the option of keeping the related
values together because it's seems better to me and also I didn't want to spend
too much time on this.
> 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)
