[
https://issues.apache.org/jira/browse/HDFS-13516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498186#comment-16498186
]
Íñigo Goiri edited comment on HDFS-13516 at 6/1/18 4:23 PM:
------------------------------------------------------------
A lot of subsequent tests fail with NPE when cleaning up, that should also be
caught.
Another example
[here|https://builds.apache.org/job/hadoop-trunk-win/484/testReport/org.apache.hadoop.ozone/TestMetadataStore/].
The errors are three:
* Could not initialize class org.rocksdb.Options
([example|https://builds.apache.org/job/hadoop-trunk-win/484/testReport/org.apache.hadoop.ozone/TestMetadataStore/testBatchWrite_1_/])
which it must be a Windows error.
* NullPointerException
([example|https://builds.apache.org/job/hadoop-trunk-win/484/testReport/org.apache.hadoop.ozone/TestMetadataStore/testBatchWrite_1__2/])
which is caused by the previous initialization issue, this should be as easy
as check for null in the cleanup.
* C:\Users\jenkins\AppData\Local\Temp\librocksdbjni6432002130619842966.dll: A
dynamic link library (DLL) initialization routine failed
([example|https://builds.apache.org/job/hadoop-trunk-win/484/testReport/org.apache.hadoop.ozone/TestMetadataStore/testDestroyDB_1_/])
which must be related to the first one.
I think this two were introduced in HDFS-12149.
[~cheersyang], [~anu], you guys wrote/committed that part, could you take a
look?
I have two theories:
# RocksDB does not work on Windows and then we should just add an assume
!Windows.
# We are leaving behind some RocksDB and we cannot close them correctly.
In any case, we should check for nulls in the cleanup.
was (Author: elgoiri):
A lot of subsequent tests fail with NPE when cleaning up, that should also be
caught.
Another example
[here|https://builds.apache.org/job/hadoop-trunk-win/484/testReport/org.apache.hadoop.ozone/TestMetadataStore/].
The errors are three:
* Could not initialize class org.rocksdb.Options
([example|https://builds.apache.org/job/hadoop-trunk-win/484/testReport/org.apache.hadoop.ozone/TestMetadataStore/testBatchWrite_1_/])
which it must be a Windows error.
* NullPointerException
([example|https://builds.apache.org/job/hadoop-trunk-win/484/testReport/org.apache.hadoop.ozone/TestMetadataStore/testBatchWrite_1__2/])
which is caused by the previous initialization issue, this should be as easy
as check for null in the cleanup.
* C:\Users\jenkins\AppData\Local\Temp\librocksdbjni6432002130619842966.dll: A
dynamic link library (DLL) initialization routine failed
([example|https://builds.apache.org/job/hadoop-trunk-win/484/testReport/org.apache.hadoop.ozone/TestMetadataStore/testDestroyDB_1_/])
which must be related to the first one.
I think this two were introduced in HDFS-12149.
[~cheersyang], [~anu], you guys wrote/committed that part, could you take a
look?
I have two theories:
# RocksDB does not work on Windows and then we should just add an assume
!Windows.
# We are leaving behind some RocksDB and we cannot close them correctly.
In any case, we should check for nulls in the cleanup.
> Ozone: TestMetadataStore fails on Windows
> -----------------------------------------
>
> Key: HDFS-13516
> URL: https://issues.apache.org/jira/browse/HDFS-13516
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Íñigo Goiri
> Priority: Major
>
> TestMetadataStore fails on Windows with the following error:
> java.lang.UnsatisfiedLinkError:
> C:\Users\jenkins\AppData\Local\Temp\1\librocksdbjni4617805071197790179.dll: A
> dynamic link library (DLL) initialization routine failed
> The report can be found
> [here|https://builds.apache.org/job/hadoop-trunk-win/449/testReport/org.apache.hadoop.ozone/TestMetadataStore/].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
