You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by GitBox <gi...@apache.org> on 2020/05/13 21:39:51 UTC

[GitHub] [incubator-hudi] xushiyan commented on pull request #1619: [MINOR] Parallelize CI tests by modules

xushiyan commented on pull request #1619:
URL: https://github.com/apache/incubator-hudi/pull/1619#issuecomment-628260195


   @bvaradar @ramachandranms thanks for chime in.. from the info @ramachandranms provides, hudi-spark-bundle report will be overwritten by the last submission and that submission should cover all modules. So previously when we have only 2 jobs (unit tests and integration tests), it is due to unit tests taking longer and covering all modules so that report was accurate. If integration test job takes longer and finishes later, coverage report will also be affected. We need to avoid this kind of dependency.
   
   When we modularize projects, by design we should be able to and encouraged to run unit tests for each module independently. The integration test then serves the purpose of checking cross-module functionalities. As for the overall coverage report, I think it should be a pure appending of all kinds of test reports without chronological overwriting. Thus, I think the setup perhaps can be improved in such way that all jobs are free to submit the reports whenever they finish and codecov  sums up all submissions.


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