Remove line numbers in stack traces dumped in recipe expectations.

Because these are literally change-detector tests. I'm pretty sure I
read a testing on the toilet about this...

Bug:
Change-Id: If1369398ecea7919bd20f4aec77cb75088b87bf5
Reviewed-on: https://chromium-review.googlesource.com/820192
Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Benjamin Pastene <bpastene@chromium.org>
20 files changed
tree: 5cc9132538b32f95fefb298284b4d88c9249fbdc
  1. infra/
  2. masters/
  3. scripts/
  4. site_config/
  5. slave/
  6. tests/
  7. third_party/
  8. .gitattributes
  9. .gitignore
  10. codereview.settings
  11. DEPS
  12. environment.cfg.py
  13. LICENSE
  14. OWNERS
  15. PRESUBMIT.py
  16. README.md
  17. 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.