ambari-dev 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-10099) Web Alerts Create Confusing Errors And Warnings
Date Tue, 17 Mar 2015 05:06:38 GMT

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

Hadoop QA commented on AMBARI-10099:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12704980/AMBARI-10099.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:red}-1 core tests{color}.  The test build failed in ambari-server 

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

This message is automatically generated.

> Web Alerts Create Confusing Errors And Warnings
> -----------------------------------------------
>
>                 Key: AMBARI-10099
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10099
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-10099.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When a web alert is triggered, whether or not a connection is made, the error messages
always indicates an invalid socket. This can be very confusing, especially when the actual
HTTP error code is being masked by the CRITICAL text.



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

Mime
View raw message