Add buildbucket build information to test.

If no buildbucket build information is provided, then the expectation
file content is dependent on the value of mastername because it used to
create a default value for the bucket name.

Bug: 1109276
Change-Id: Ibd867e7c680b69874f1b8fe92a891c78981a51b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2427304
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Liviu Rau <liviurau@chromium.org>
Commit-Queue: Liviu Rau <liviurau@chromium.org>
2 files changed
tree: 68a38f45ed3055f39dfdc7dc108b3015f00d5e68
  1. infra/
  2. recipes/
  3. scripts/
  4. site_config/
  5. third_party/
  6. .gitattributes
  7. .gitignore
  8. .style.yapf
  9. .vpython
  10. .yapfignore
  11. codereview.settings
  12. CROS_OWNERS
  13. DEPS
  14. environment.cfg.py
  15. LICENSE
  16. OWNERS
  17. PRESUBMIT.py
  18. README.md
  19. WATCHLISTS
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 --no-clang-format) to autoformat new code.