Bisect - Catch error and output debugging first

Originally just tried to print these out, had to switch to outputting
them into a step. Realized that there's an exception thrown and we're
not getting the output so catching that and then re-raising it.

TBR=dtu@chromium.org
Bug: 893488
Change-Id: I8dd19ae0809c403d22864f633484f6af769a823e
Reviewed-on: https://chromium-review.googlesource.com/c/1278006
Commit-Queue: Simon Hatch <simonhatch@chromium.org>
Reviewed-by: Simon Hatch <simonhatch@chromium.org>
1 file changed
tree: 513332ddf469b82a517300829be777b12479a57d
  1. infra/
  2. masters/
  3. scripts/
  4. site_config/
  5. slave/
  6. tests/
  7. third_party/
  8. .gitattributes
  9. .gitignore
  10. .vpython
  11. codereview.settings
  12. DEPS
  13. environment.cfg.py
  14. LICENSE
  15. OWNERS
  16. PRESUBMIT.py
  17. README.md
  18. WATCHLISTS
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.