[
https://issues.apache.org/jira/browse/HDFS-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445315#comment-13445315
]
Hadoop QA commented on HDFS-3833:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12543138/HDFS-3833.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
-1 findbugs. The patch appears to introduce 1 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 in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.TestHftpDelegationToken
org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics
org.apache.hadoop.hdfs.server.datanode.TestBPOfferService
org.apache.hadoop.hdfs.TestPersistBlocks
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/3126//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/3126//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3126//console
This message is automatically generated.
> TestDFSShell fails on Windows due to file concurrent read write
> ---------------------------------------------------------------
>
> Key: HDFS-3833
> URL: https://issues.apache.org/jira/browse/HDFS-3833
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 3.0.0, 1-win
> Reporter: Brandon Li
> Assignee: Brandon Li
> Attachments: HDFS-3833.branch-1-win.patch, HDFS-3833.patch
>
>
> TestDFSShell sometimes fails due to the race between the write issued by the
> test and blockscanner. Example stack trace:
> {noformat}
> Error Message
> c:\A\HM\build\test\data\dfs\data\data1\current\blk_-7735708801221347790 (The
> requested operation cannot be performed on a file with a user-mapped section
> open)
> Stacktrace
> java.io.FileNotFoundException:
> c:\A\HM\build\test\data\dfs\data\data1\current\blk_-7735708801221347790 (The
> requested operation cannot be performed on a file with a user-mapped section
> open)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:194)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:145)
> at java.io.PrintWriter.<init>(PrintWriter.java:218)
> at org.apache.hadoop.hdfs.TestDFSShell.corrupt(TestDFSShell.java:1133)
> at org.apache.hadoop.hdfs.TestDFSShell.testGet(TestDFSShell.java:1231)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
