[
https://issues.apache.org/jira/browse/HDDS-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17442533#comment-17442533
]
Rakesh Radhakrishnan commented on HDDS-5819:
--------------------------------------------
Thanks [~erose], good catch. I also thinks that {{testRenameToTrashEnabled}}
has failed firstly then induced errors to other test cases.
Along with the {{{}testRenameToTrashEnabled fix, c{}}}an you please add logic
to cleanup of all garbage/paths created by each test case after its execution,
especially in failure case. This will avoid unwanted noise to other test cases
and can narrow down the failure quickly, in future.
How about introducing an {{@After}} teardown() method and do cleanup paths,
something like:
{code:java}
public void teardown() {
Path root = new Path("/" + volumeName + "/" + bucketName);
FileStatus[] fileStatuses = fs.listStatus(root);
for(int i=0; i<fileStatuses.length; i++){
fs.delete(fileStatuses[i].getPath(), true);
}
}
{code}
> Intermittent failures in TestRootedOzoneFileSystem
> --------------------------------------------------
>
> Key: HDDS-5819
> URL: https://issues.apache.org/jira/browse/HDDS-5819
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ethan Rose
> Assignee: Ke-Yi Sung
> Priority: Major
> Attachments: it-filesystem-hdds.zip
>
>
> TestRootedOzoneFileSystem reuses the same MiniOzoneCluster for all runs. A
> cascading series of failures was observed in this CI run:
> [https://github.com/apache/ozone/runs/3792440274]
> It looks like testRenameToTrashEnabled was the original failure that caused
> the others. Looking in the logs (attached in the zip file) there are numerous
> volume and bucket request errors that may have resulted in this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
