[jira] [Commented] (HBASE-15917) Flaky tests dashboard
[ https://issues.apache.org/jira/browse/HBASE-15917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308502#comment-15308502 ] Hudson commented on HBASE-15917: FAILURE: Integrated in HBase-Trunk_matrix #961 (See [https://builds.apache.org/job/HBase-Trunk_matrix/961/]) HBASE-15917 Addendum. Fix bug in report-flakies.py where hanging tests (stack: rev eb64cd9dd13ba297539c409989c63e800cb378a1) * dev-support/report-flakies.py > 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 > Fix For: 2.0.0 > > Attachments: HBASE-15917.master.001.addendum.patch, > HBASE-15917.master.001.addendum2.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 > *(See [this external link|http://hbase.x10host.com/flaky-tests/] for pretty > version.)* > 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)
[jira] [Commented] (HBASE-15917) Flaky tests dashboard
[
https://issues.apache.org/jira/browse/HBASE-15917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308129#comment-15308129
]
Dima Spivak commented on HBASE-15917:
-
Some mostly nit-y Python comments:
* Instead of documenting functions with leading {{ \# }}s, use triple
double-quotes for docstrings (see PEP 257).
* {{get_bad_tests}} might work better returning a tuple than a list since you
probably want this immutable.
* Replace {{print}}s with logging objects when applicable (e.g. for script
status updates).
* Move the HTML template to its own file instead of putting it inline. We
should probably do the same with the stylesheet, too.
Really cool idea here, [~appy]. Good work.
> 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.addendum2.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
> *(See [this external link|http://hbase.x10host.com/flaky-tests/] for pretty
> version.)*
> 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)
[jira] [Commented] (HBASE-15917) Flaky tests dashboard
[ https://issues.apache.org/jira/browse/HBASE-15917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307339#comment-15307339 ] Hudson commented on HBASE-15917: FAILURE: Integrated in HBase-Trunk_matrix #960 (See [https://builds.apache.org/job/HBase-Trunk_matrix/960/]) HBASE-15917 Flaky tests dashboard. (Apekshit) (stack: rev 0923346b6117e5dc0f9d18f4c00d7fd5fe816367) * dev-support/report-flakies.py * dev-support/findHangingTests.py HBASE-15917 Addendum. Add jija2 to python requirements. It's used by (stack: rev f0a1e22441e6ead196c558ac4b16b17697a036fd) * dev-support/python-requirements.txt > 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 > *(See [this external link|http://hbase.x10host.com/flaky-tests/] for pretty > version.)* > 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)
[jira] [Commented] (HBASE-15917) Flaky tests dashboard
[
https://issues.apache.org/jira/browse/HBASE-15917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (HBASE-15917) Flaky tests dashboard
[
https://issues.apache.org/jira/browse/HBASE-15917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307151#comment-15307151
]
Hadoop QA commented on HBASE-15917:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} pylint {color} | {color:blue} 0m 3s
{color} | {color:blue} Pylint was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
25m 22s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
11s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 25m 41s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12807030/HBASE-15917.master.001.patch
|
| JIRA Issue | HBASE-15917 |
| Optional Tests | asflicense pylint |
| uname | Linux asf907.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / e6d613d |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/2062/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.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)
