[
https://issues.apache.org/jira/browse/HADOOP-14249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945314#comment-15945314
]
Steve Loughran commented on HADOOP-14249:
-----------------------------------------
Fix is straightforward: use the method name in generating the contract test path
Other workarounds (e.g override deleteTestDirInTeardown or not call superclass
stuff will hide the problem; best to make sure that every test case has a
unique filename (or at least unique except in the special case of subclassed
tests running in parallel)
I'm seeing this in HADOOP-13786; the more threads I have, the more often it
surfaces
> s3a test teardown can delete entire path
> ----------------------------------------
>
> Key: HADOOP-14249
> URL: https://issues.apache.org/jira/browse/HADOOP-14249
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3, test
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
>
> This has existed for a while, it's just not anything we've explicitly noticed.
> {{AbstractFSContractTestBase.teardown()}} calls
> {{deleteTestDirInTeardown()}}, which deletes the test directory supplied by
> the S3a contract, which is that of the base /test path or the fork method
> which means that when one test suite tears down, it can delete the test
> directory of other tests still running.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
