hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15917) Flaky tests dashboard
Date Tue, 31 May 2016 04:19:12 GMT

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

Hadoop QA commented on HBASE-15917:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 3s {color} | {color:red}
HBASE-15917 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.2.1/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12807035/HBASE-15917.master.001.addendum.patch
|
| JIRA Issue | HBASE-15917 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/2064/console |
| Powered by | Apache Yetus 0.2.1   http://yetus.apache.org |


This message was automatically generated.



> Flaky tests dashboard
> ---------------------
>
>                 Key: HBASE-15917
>                 URL: https://issues.apache.org/jira/browse/HBASE-15917
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Appy
>            Assignee: Appy
>         Attachments: HBASE-15917.master.001.addendum.patch, HBASE-15917.master.001.patch
>
>
> report-flakies.py now outputs a file dashboard.html.
> Then the dashboard will always be accessible from https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html
> Currently it shows:
> Failing tests
> flakyness %
> count of times a test failed, timed out or hanged
> Links to jenkins' runs grouped by whether the test succeeded, failed, timed out and was
hanging in that run.
> Also, once we have set timeouts to tests, they'll not be "hanging" anymore since they'll
fail with timeout. Handle this minor difference in findHangingTests.py and show the corresponding
stats in dashboard.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message