hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Appy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16384) Update report-flakies.py script to allow specifying a list of build ids to be excluded
Date Tue, 09 Aug 2016 22:14:21 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414333#comment-15414333
] 

Appy commented on HBASE-16384:
------------------------------

So basically consider this example:
--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"

So first, I think it's clean.
Also, if we split into three options, --urls ,--excludes and --max-builds, i think it'll make
things much worse.



> 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)

Mime
View raw message