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

Siyao Meng resolved HDDS-5986.
------------------------------
    Resolution: Duplicate

> TestRootedOzoneFileSystem does not properly initialize clusters for tests
> -------------------------------------------------------------------------
>
>                 Key: HDDS-5986
>                 URL: https://issues.apache.org/jira/browse/HDDS-5986
>             Project: Apache Ozone
>          Issue Type: Test
>            Reporter: István Fajth
>            Priority: Major
>
> The TestRootedOzoneFileSystem class is a parametrized test, similarly to 
> TestRootedOzoneFileSystemWithFSO which is a child class.
> The minicluster underneath the test is not re-initialized between runs, hence 
> configuration changes are not applied, and the cluster is initialized with 
> default values for those properties, even though they are later set in the 
> constructor.
> In order to solve this problem the following can be done:
> Change @BeforeClass and @AfterClass annotation on the init() and teardown() 
> method to @Parametrized.BeforeParam, and @Parametrized.AfterParam, and add 
> the three boolean param to the init method and initialize the variables 
> there, then the cluster for every run in the test. (The init method will be 
> called by the Parametrized runner at the proper time after annotation is 
> changed.)
> Doing this change fails a few tests in TestRootedOzoneFileSystem 
> (testDeleteCreatesFakeParentDirKeys, testMkdirOnNonExistentVolumeBucketDir, 
> testListStatusOnLargeDirectory, testListStatusInBucket).
> In order to fix the initialization of the cluster, we need to fix these tests 
> as well. These are failing when enableOfsPath is properly set to true in the 
> first three test sets.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to