Fix deleted builder detection in chromium/targets_config_verifier.

crrev.com/c/5847630 updated the recipe to detect builders that were
being deleted and not try to verify them. Unfortunately because it was
using a path relative to the repo root, the properties file would never
show up as existing, so for any builder where the properties file was
modified, it would be treated as though the builder was deleted. This
updates the check to correctly root the properties file path to the
repo.

Bug: 40258588
Change-Id: I90c5a6590edde0b0365c2fbb4ba4058df6aef955
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/5886953
Commit-Queue: Garrett Beaty <gbeaty@google.com>
Auto-Submit: Garrett Beaty <gbeaty@google.com>
Commit-Queue: Stephanie Kim <kimstephanie@google.com>
Reviewed-by: Stephanie Kim <kimstephanie@google.com>
1 file changed
tree: a7a941bd9b3d9d64bcf7cc0b3866caaea2575786
  1. hook-scripts/
  2. infra/
  3. recipes/
  4. scripts/
  5. .gitattributes
  6. .gitignore
  7. .style.yapf
  8. .vpython3
  9. .yapfignore
  10. codereview.settings
  11. DEPS
  12. LICENSE
  13. OWNERS
  14. PRESUBMIT.py
  15. PRESUBMIT_test.py
  16. README.md
README.md

Recipes

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

Style

The preferred style is PEP8 with two-space indent. Functions use lowercase_with_underscores, with the exception of the special functions RunSteps and RunTests in recipes. Use yapf (git cl format --no-clang-format) to autoformat new code.