[recipe test utils] Consistently save full result information.

This is needed so that users can get access to per-test fields
such as "shard". See full plan at
https://bugs.chromium.org/p/chromium/issues/detail?id=960951#c2

Currently it looks like these fields are only used for their keys(),
i.e. test_results.unexpected_failures.keys().

Bug: 960951
Change-Id: Ida9f21fd784e2ce42bd9a449646b5256f1a5e1df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1620673
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Auto-Submit: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
1 file changed
tree: 535d76c488e6abcdf848dbd045efa867d404a4ac
  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.