[
https://issues.apache.org/jira/browse/HADOOP-17385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17234940#comment-17234940
]
Steve Loughran commented on HADOOP-17385:
-----------------------------------------
PR in. FWIW, I don't see why this didn't surface on test runs on the
HADOOP-13718 patch, unless changes in HADOOP-17244 changed parameter execution
enough that the failing test setup was now running first. If invoked in a JVM
on second or later iteration then the loader wouldn't show.
> ITestS3ADeleteCost.testDirMarkersFileCreation failure
> -----------------------------------------------------
>
> Key: HADOOP-17385
> URL: https://issues.apache.org/jira/browse/HADOOP-17385
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test runs after apply of recent patches HADOOP-17318 and HADOOP-17244 are
> showing a failure in ITestS3ADeleteCost.testDirMarkersFileCreation
> Either one of the patches is failing and wasn't picked up, or the combined
> changes are conflicting in some way. Not backporting HADOOP-17318 to
> branch-3.3 until this is addressed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]