[
https://issues.apache.org/jira/browse/HBASE-19030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211148#comment-16211148
]
Hadoop QA commented on HBASE-19030:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 3m
12s{color} | {color:red} Docker failed to build yetus/hbase:4a7b430. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-19030 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893053/HBASE-19030.0.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9219/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> nightly runs should attempt to log test results after archiving
> ---------------------------------------------------------------
>
> Key: HBASE-19030
> URL: https://issues.apache.org/jira/browse/HBASE-19030
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Critical
> Attachments: HBASE-19030.0.patch
>
>
> right now on the nightly tests the first post-action we do is log junit
> results. due to current limitations of Jenkins DSL, if this step fails none
> of the other post actions will happen.
> Since we might not make junit test results, e.g. in the case of a timeout of
> yetus itself, we should log the junit results after we've saved whatever we
> can of yetus output.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
