You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/04/03 12:08:57 UTC

[GitHub] [hadoop-ozone] elek commented on issue #750: HDDS-3309. Add timeout to all integration tests

elek commented on issue #750: HDDS-3309. Add timeout to all integration tests
URL: https://github.com/apache/hadoop-ozone/pull/750#issuecomment-608398011
 
 
   Thanks the patch @smengcl This timeouts (and especially the root cause) the biggest problem with the integration tests right now... 
   
   > This helps ruling out flaky long-running tests (e.g. TestRandomKeyGenerator.bigFileThan2GB) that are taking a very long time to run in Github actions.
   
   Did you see any long running integration tests?
   
   It seems that we have a global timeout:
   
   In the main `pom.xml`:
   ```
     <surefire.fork.timeout>900</surefire.fork.timeout>
   ...
     <forkedProcessTimeoutInSeconds>${surefire.fork.timeout}</forkedProcessTimeoutInSeconds>
   ```
   
   Isn't it easier to decrease this number? (If I understand well it does the same as we fork the JVM)
   
   Did you check the current execution time of all the integration tests? Is the proposed value is significant bigger than the expected time of the slowest test?

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org