[ResultDB] Include invocations then exonerate

We should include invocations as soon as they are derived, then do exoneration. Invocation inclusion should never be blocked by failures of exoneration.

Bug: 1081225
Change-Id: Ib53a010d0794e7de680d60b3db69ab27e80128c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2290198
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
Reviewed-by: Nodir Turakulov <nodir@chromium.org>
Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Commit-Queue: Chan Li <chanli@chromium.org>
2 files changed
tree: c5d581fe90cbc57068ea98bf75e8593a1d013d81
  1. .gitattributes
  2. .gitignore
  3. .style.yapf
  4. .vpython
  5. .yapfignore
  6. CROS_OWNERS
  7. DEPS
  8. LICENSE
  9. OWNERS
  10. PRESUBMIT.py
  11. README.md
  12. WATCHLISTS
  13. codereview.settings
  14. environment.cfg.py
  15. infra/
  16. scripts/
  17. site_config/
  18. third_party/
README.md

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.

Style

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