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/01/06 10:59:38 UTC

[GitHub] [hadoop-ozone] elek commented on issue #383: HDDS-2785. Move ozonefs and tools minicluster tests to integration-test

elek commented on issue #383: HDDS-2785. Move ozonefs and tools minicluster tests to integration-test
URL: https://github.com/apache/hadoop-ozone/pull/383#issuecomment-571096821
 
 
   Thanks the patch @adoroszlai. I like the approach to reverse the dependency (and simplify `acceptance.sh` and `unit.sh`), but I would prefer to keep the feature to separate certain type of integration tests as in this branch/runs:
   
   https://github.com/apache/hadoop-ozone/runs/373475163
   
   The test execution of integration-test project is already very slow, we can make it faster with separating contract/tools tests. I am not sure how to do it in this new structure. We have multiple options:
   
   1. put everything to the `integration-test` and use profiles to separate tests
   2. create separated `integration-test/contract` and `integration-test/tools` projects
   3. Keep the tests in the original projects and use the maven `integration-test` phase to execute these tests.
   
   What is your preference?
   

----------------------------------------------------------------
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