ambari-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] (AMBARI-18982) Failures due to timeout don't report any reason
Date Thu, 24 Nov 2016 09:37:58 GMT

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

Hadoop QA commented on AMBARI-18982:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12840388/AMBARI-18982.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/9384//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/9384//console

This message is automatically generated.

> Failures due to timeout don't report any reason
> -----------------------------------------------
>
>                 Key: AMBARI-18982
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18982
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18982.patch
>
>
> Just to find out that install task was canceled due to timeout me and Dmytro Grinenko
had to do a half an hour debugging including running though java code, just to find out the
failure reason.
> The failure reason should be obvious and always printed printed to task stderr/stdout
so user can see it.



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

Mime
View raw message