hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giovanni Matteo Fumarola (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13550) TestDebugAdmin#testComputeMetaCommand fails on Windows
Date Wed, 16 May 2018 16:54:00 GMT

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

Giovanni Matteo Fumarola commented on HDFS-13550:
-------------------------------------------------

Thanks [~huanbang1993] for taking care of this. LGTM +1.

[~elgoiri], we should consider replacing in the codebase all the "/n" hardcoded ones with
{{System.lineSeparator}}.

> TestDebugAdmin#testComputeMetaCommand fails on Windows
> ------------------------------------------------------
>
>                 Key: HDFS-13550
>                 URL: https://issues.apache.org/jira/browse/HDFS-13550
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Anbang Hu
>            Assignee: Anbang Hu
>            Priority: Major
>              Labels: Windows
>         Attachments: HDFS-13550.000.patch, HDFS-13550.001.patch
>
>
> {color:#d04437}[INFO] Running org.apache.hadoop.hdfs.tools.TestDebugAdmin{color}
> {color:#d04437}[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
32.845 s <<< FAILURE! - in org.apache.hadoop.hdfs.tools.TestDebugAdmin{color}
> {color:#d04437}[ERROR] testComputeMetaCommand(org.apache.hadoop.hdfs.tools.TestDebugAdmin)
Time elapsed: 32.792 s <<< FAILURE!{color}
> {color:#d04437}org.junit.ComparisonFailure:{color}
> {color:#d04437}expected:<...file, and save it to[ the specified output metadata file.**NOTE:
Use at your own risk! If the block file is corrupt and you overwrite it's meta file, it will
show up as good in HDFS, but you can't read the data. Only use as a last measure, and when
you are 100% certain the block file is good.]> but was:<...file, and save it to[{color}
> {color:#d04437} the specified output metadata file.{color}
> {color:#d04437}**NOTE: Use at your own risk!{color}
> {color:#d04437} If the block file is corrupt and you overwrite it's meta file,{color}
> {color:#d04437} it will show up as good in HDFS, but you can't read the data.{color}
> {color:#d04437} Only use as a last measure, and when you are 100% certain the block file
is good.{color}
> {color:#d04437}]>{color}
> {color:#d04437} at org.junit.Assert.assertEquals(Assert.java:115){color}
> {color:#d04437} at org.junit.Assert.assertEquals(Assert.java:144){color}
> {color:#d04437} at org.apache.hadoop.hdfs.tools.TestDebugAdmin.testComputeMetaCommand(TestDebugAdmin.java:137){color}
> {color:#d04437} at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){color}
> {color:#d04437} at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62){color}
> {color:#d04437} at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){color}
> {color:#d04437} at java.lang.reflect.Method.invoke(Method.java:498){color}
> {color:#d04437} at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47){color}
> {color:#d04437} at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12){color}
> {color:#d04437} at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44){color}
> {color:#d04437} at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17){color}
> {color:#d04437} at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74){color}
> {color:#d04437}[INFO]{color}
> {color:#d04437}[INFO] Results:{color}
> {color:#d04437}[INFO]{color}
> {color:#d04437}[ERROR] Failures:{color}
> {color:#d04437}[ERROR] TestDebugAdmin.testComputeMetaCommand:137 expected:<...file,
and save it to[ the specified output metadata file.**NOTE: Use at your own risk! If the block
file is corrupt and you overwrite it's meta file, it will show up as good in HDFS, but you
can't read the data. Only use as a last measure, and when you are 100% certain the block file
is good.]> but was:<...file, and save it to[{color}
> {color:#d04437} the specified output metadata file.{color}
> {color:#d04437}**NOTE: Use at your own risk!{color}
> {color:#d04437} If the block file is corrupt and you overwrite it's meta file,{color}
> {color:#d04437} it will show up as good in HDFS, but you can't read the data.{color}
> {color:#d04437} Only use as a last measure, and when you are 100% certain the block file
is good.{color}
> {color:#d04437}]>{color}
> {color:#d04437}[INFO]{color}
> {color:#d04437}[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message