[
https://issues.apache.org/jira/browse/HDFS-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486675#comment-14486675
]
Hadoop QA commented on HDFS-8103:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12724077/HDFS-8103.000.patch
against trunk revision dc0282d.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
See
https://builds.apache.org/job/PreCommit-HDFS-Build/10223//artifact/patchprocess/diffJavadocWarnings.txt
for details.
{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 2.0.3) 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 patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.blockmanagement.TestDatanodeManager
org.apache.hadoop.hdfs.TestRollingUpgrade
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/10223//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HDFS-Build/10223//console
This message is automatically generated.
> Move BlockTokenSecretManager.AccessMode into BlockTokenIdentifier
> -----------------------------------------------------------------
>
> Key: HDFS-8103
> URL: https://issues.apache.org/jira/browse/HDFS-8103
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: build
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Priority: Minor
> Attachments: HDFS-8103.000.patch
>
>
> The {{AccessMode}} enum is used by both the server and the client. It should
> belong to {{BlockTokenIdentifier}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)