You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/09/14 21:10:50 UTC

[GitHub] [beam] MarcoRob commented on pull request #23138: GA Migration Java PreCommit

MarcoRob commented on PR #23138:
URL: https://github.com/apache/beam/pull/23138#issuecomment-1247306400

   Hi @damccorm 
   I am reaching out to validate the current approach for the `Java Pre-commit Job`. Right now we are handling the tests of the workflow in a matrix (https://github.com/apache/beam/blob/096fb6900a747aff7ae21865d578dab8157ea379/.github/workflows/job-precommit-java.yml). This allows us to have one job per test and be able to run them individually in case they fail, but this also means that for each test inside the matrix one runner/pod will be generated.
   So for example, the way we separated the JavaPrecommit workflow (tests listed inside a matrix), the total number of jobs/runners will be 40ish.
   If we add just one job for all the tests, only one runner will be created, but we lose the option of executing only the test/job that failed. 
   I would like to know your thoughts on this matter. Ty
   cc: @fernando-wizeline @benWize @andoni-guzman 


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

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org