[
https://issues.apache.org/jira/browse/HADOOP-10332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897296#comment-13897296
]
Hadoop QA commented on HADOOP-10332:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12628097/HADOOP-10332.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) 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
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3553//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3553//console
This message is automatically generated.
> HttpServer's jetty audit log always logs 200 OK
> -----------------------------------------------
>
> Key: HADOOP-10332
> URL: https://issues.apache.org/jira/browse/HADOOP-10332
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Jonathan Eagles
> Attachments: HADOOP-10332-branch-0.23.patch, HADOOP-10332.patch
>
>
> HttpServer inserts the audit logger handler _before_ the actual servlet
> handlers, so the default 200 is always logged even if the operation fails.
> {code}
> handlers.setHandlers(new Handler[] {requestLogHandler, contexts});
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
