[ 
https://issues.apache.org/jira/browse/HADOOP-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal resolved HADOOP-9428.
-----------------------------------

    Resolution: Duplicate
    
> TestNativeIO#testRenameTo is broken on Windows
> ----------------------------------------------
>
>                 Key: HADOOP-9428
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9428
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>              Labels: windows
>             Fix For: 3.0.0
>
>
> Exception details:
> testRenameTo(org.apache.hadoop.io.nativeio.TestNativeIO)  Time elapsed: 16 
> sec  <<< FAILURE!
> java.lang.AssertionError: expected:<UNKNOWN> but was:<ENOENT>
>       at org.junit.Assert.fail(Assert.java:91)
>       at org.junit.Assert.failNotEquals(Assert.java:645)
>       at org.junit.Assert.assertEquals(Assert.java:126)
>       at org.junit.Assert.assertEquals(Assert.java:145)
>       at 
> org.apache.hadoop.io.nativeio.TestNativeIO.testRenameTo(TestNativeIO.java:423)
>       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:44)
>       at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>       at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>       at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>       at 
> org.junit.internal.runners.statements.FailOnTimeout$1.run(FailOnTimeout.java:28)

--
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

Reply via email to