[
https://issues.apache.org/jira/browse/HDFS-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216090#comment-13216090
]
Hadoop QA commented on HDFS-3006:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12515975/h3006_20120224c.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hdfs.server.common.TestDistributedUpgrade
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/1908//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1908//console
This message is automatically generated.
> Webhdfs "SETOWNER" call returns incorrect content-type
> ------------------------------------------------------
>
> Key: HDFS-3006
> URL: https://issues.apache.org/jira/browse/HDFS-3006
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.2
> Reporter: bc Wong
> Assignee: Tsz Wo (Nicholas), SZE
> Attachments: h3006_20120223.patch, h3006_20120224.patch,
> h3006_20120224b.patch, h3006_20120224c.patch
>
>
> The SETOWNER call returns an empty body. But the header has "Content-Type:
> application/json", which is a contradiction (empty string is not valid json).
> This appears to happen for SETTIMES and SETPERMISSION as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
