commit 032786d46b16a2cfc704445af09b76b4adfe759b
author chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Mon Jul 29 19:52:12 2019
committer Commit Bot <commit-bot@chromium.org> Mon Jul 29 19:52:12 2019
tree fca5ce2fbf9b116e7f4217e67fa29c34772cef96
parent 587a06cd3fac63abb5adbbaf8e05097432c18186

Roll src/third_party/chromite 51f067298563..e9417eb6e06b (1 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/51f067298563..e9417eb6e06b


git log 51f067298563..e9417eb6e06b --date=short --no-merges --format='%ad %ae %s'
2019-07-29 jorgelo@chromium.org usergroup_baseline.py: Add security team as OWNERS.


Created with:
  gclient setdep -r src/third_party/chromite@e9417eb6e06b

The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel

TBR=chrome-os-gardeners@google.com

Bug: None
Change-Id: Ie11ee7e3546c8f5589a2b188de9a8c08d20cd12b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723580
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#681933}