hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5103) TestDirectoryScanner fails on Windows
Date Fri, 16 Aug 2013 14:46:54 GMT

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

Hudson commented on HDFS-5103:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1520 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1520/])
HDFS-5103. TestDirectoryScanner fails on Windows. Contributed by Chuan Liu. (cnauroth: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1514576)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDirectoryScanner.java

                
> TestDirectoryScanner fails on Windows
> -------------------------------------
>
>                 Key: HDFS-5103
>                 URL: https://issues.apache.org/jira/browse/HDFS-5103
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 3.0.0, 2.1.1-beta
>            Reporter: Chuan Liu
>            Assignee: Chuan Liu
>            Priority: Minor
>             Fix For: 3.0.0, 2.1.1-beta
>
>         Attachments: HDFS-5103-trunk.patch
>
>
> TestDirectoryScanner fails on Windows due to mixed use of Windows path and Unix path.
> {noformat}
> org.junit.ComparisonFailure: expected:<[/base/current/BP-783049782-127.0.0.1-1370971773491/]finalized>
but was:<[C:\base\current\BP-783049782-127.0.0.1-1370971773491\]finalized>
> 	at org.junit.Assert.assertEquals(Assert.java:125)
> 	at org.junit.Assert.assertEquals(Assert.java:147)
> 	at org.apache.hadoop.hdfs.server.datanode.TestDirectoryScanner.testScanInfoObject(TestDirectoryScanner.java:419)
> 	at org.apache.hadoop.hdfs.server.datanode.TestDirectoryScanner.TestScanInfo(TestDirectoryScanner.java:449)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> 	at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> {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

Mime
View raw message