[ https://issues.apache.org/jira/browse/HBASE-16384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414330#comment-15414330 ]
Dima Spivak commented on HBASE-16384: ------------------------------------- Why not just pass in a single URL and take separate arguments for specific build numbers to exclude and the maximum number of builds to analyze? I think simplifying the tool at the cost of a slight amount of flexibility during invocation would make it much easier to use. e.g. {noformat} ./report-flakies.py --url=my_build --excluded-builds=[12,13,14] --max-builds=20 {noformat} > 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)