[
https://issues.apache.org/jira/browse/HDFS-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967536#comment-13967536
]
Hudson commented on HDFS-6235:
------------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1755 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1755/])
HDFS-6235. TestFileJournalManager can fail on Windows due to file locking if
tests run out of order. Contributed by Chris Nauroth. (cnauroth:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1586692)
* /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/namenode/TestFileJournalManager.java
> TestFileJournalManager can fail on Windows due to file locking if tests run
> out of order.
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-6235
> URL: https://issues.apache.org/jira/browse/HDFS-6235
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode, test
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Trivial
> Fix For: 3.0.0, 2.4.1
>
> Attachments: HDFS-6235.1.patch
>
>
> {{TestFileJournalManager}} has multiple tests that reuse the same storage
> directory: /filejournaltest2. The last test in the suite intentionally
> leaves a file open to test behavior of an unclosed edit log. On some
> environments though, tests within a suite execute out of order. In this
> case, a lock is still held on /filejournaltest2, and subsequent tests fail
> trying to delete the directory.
--
This message was sent by Atlassian JIRA
(v6.2#6252)