hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Radia (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8534) Some tests leave a config file open causing failure on windows
Date Tue, 03 Jul 2012 00:22:57 GMT

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

Sanjay Radia updated HADOOP-8534:

    Summary: Some tests leave a config file open causing failure on windows  (was: TestQueueManagerForJobKillAndJobPriority
and TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows)
> Some tests leave a config file open causing failure on windows
> --------------------------------------------------------------
>                 Key: HADOOP-8534
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8534
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 1.0.0
>            Reporter: Ivan Mitic
>            Assignee: Ivan Mitic
>         Attachments: HADOOP-8534-branch-1-win_Parser(2).patch, HADOOP-8534-branch-1-win_Parser.patch
> Java xml parser keeps file locked after SAXException, causing the following tests to
>  - TestQueueManagerForJobKillAndJobPriority
>  - TestQueueManagerForJobKillAndNonDefaultQueue
> {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}}
is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup
this file and this operation fails on Windows (as the file is still open). From this point
on, all subsequent tests fail because they try to use the incorrect config file.
> Forum references on the problem and the fix:
> http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
> https://forums.oracle.com/forums/thread.jspa?threadID=2046505&start=0&tstart=0

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message