[chromium_tests] extract the logic to determine compilation targets

During calculation of tests to run, the bot determines the compile and test
targets and depending on bot type (CI/Try), it prunes the targets. This logic
lives inside the long `_calculate_tests_to_run` function.

This CL extracts the logic to determine compilation targets out of
`_calculate_tests_to_run` into `_determine_compilation_targets`

R=jbudorick@chromium.org

Bug: 950731
Change-Id: I3c2f90e04558086b0dfb0c59419b1bb96809e827
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1617224
Commit-Queue: Tamer Tas <tmrts@chromium.org>
Auto-Submit: Tamer Tas <tmrts@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
1 file changed
tree: 2784e24f4ceca3f229e120bb9d93731de6bdd5ed
  1. .gitattributes
  2. .gitignore
  3. .vpython
  4. DEPS
  5. LICENSE
  6. OWNERS
  7. PRESUBMIT.py
  8. README.md
  9. WATCHLISTS
  10. codereview.settings
  11. environment.cfg.py
  12. infra/
  13. masters/
  14. scripts/
  15. site_config/
  16. slave/
  17. tests/
  18. third_party/
README.md

build

Hi build contributor! If you do any change in scripts/master/ or touching any master's html/ directories, you must restart master.chromium.fyi first and ensure that it still works before restarting other masters.

Recipes

If you're here to make a change to ‘recipes’ (the code located in scripts/slave/recipes*), please take a look at the README for more information pertaining to recipes.