commit 816f435df2429f423b051437f69d0fb51f6eb81a
author chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Sat May 11 18:15:52 2019
committer Commit Bot <commit-bot@chromium.org> Sat May 11 18:15:52 2019
tree c25bce7f37eef841a90739c5928b23ffb62aea92
parent d1e1f1f0ebd481812dd91d1a1143a75f1bdc56e6

Roll src/third_party/chromite ef7e8df62225..73eee452fa09 (1 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/ef7e8df62225..73eee452fa09


git log ef7e8df62225..73eee452fa09 --date=short --no-merges --format='%ad %ae %s'
2019-05-11 jclinton@chromium.org Revert the -1 hack now that we have a whitelist facility


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

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

Change-Id: I97ca7ddd3dbc7c27b2577c6246cd103ce0a23e6e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1607673
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@{#658900}