smengcl commented on pull request #1286: URL: https://github.com/apache/hadoop-ozone/pull/1286#issuecomment-670082854
I ran `TestRootedOzoneFileSystem` locally again. It seems the problem is it is taking significant longer (double the time spent) to run the test with the parameter (14m 52s total for both, about 7m 30s for each) than without the parameter (7m 47s). Good new is all tests pass. Another observation. On the GH workflow run, without parameterization we were spending around 9.5min for `TestRootedOzoneFileSystem` without parameterization: https://github.com/apache/hadoop-ozone/runs/941577903 ``` [INFO] Running org.apache.hadoop.fs.ozone.TestOzoneFileSystem [INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 251.496 s - in org.apache.hadoop.fs.ozone.TestOzoneFileSystem ... [INFO] Running org.apache.hadoop.fs.ozone.TestRootedOzoneFileSystem [INFO] Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 566.177 s - in org.apache.hadoop.fs.ozone.TestRootedOzoneFileSystem ... [INFO] Running org.apache.hadoop.fs.ozone.TestOzoneFileInterfaces [WARNING] Tests run: 18, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 381.674 s - in org.apache.hadoop.fs.ozone.TestOzoneFileInterfaces ``` With parameterization we can expect it to be spending over 1100s (18min) on this one test suite.. which is not good. We will need to reduce the run time of the test suite. Probably should do this in another jira. Also I haven't figured out where the timeout is imposed as of now. @adoroszlai Do you know where [this](https://github.com/apache/hadoop-ozone/runs/946974224) 45m-46m timeout is imposed? @bharatviswa504 Now that we can prove the tests work with both `ozone.om.enable.filesystem.paths` options. Should we proceed with fdbc71cdabcfa846d538878f80bb602a37a63528 ? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
