commit 1a05b76cf1e92a2bdec4db65b9a675cf8df9c568
author Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Wed Jun 06 01:15:54 2018
committer Commit Bot <commit-bot@chromium.org> Wed Jun 06 01:15:54 2018
tree e57046493911138629bb34924c00e986380c7190
parent 06f66cde750e1f388e19a0390214bb988eed1768

Roll src/third_party/chromite 3c46387..784bb7f (5 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/3c46387..784bb7f


git log 3c46387..784bb7f --date=short --no-merges --format='%ad %ae %s'
2018-06-05 vapier@chromium.org cros lint: rework extension/linter lookups
2018-06-05 bmgordon@chromium.org cros_build_lib: Catch additional gethostbyaddr exception
2018-06-05 bpastene@chromium.org chromite: Roll third_party/gn_helpers forward.
2018-06-05 vapier@chromium.org qemu: fix bug in registration logic
2018-06-05 vapier@chromium.org qemu: add more logging around registration


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

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

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.



BUG=chromium:None,chromium:None,chromium:824808,chromium:824808
TBR=chrome-os-gardeners@chromium.org

Change-Id: I122486e1710bce26bd16709b9d5c6d401cdb9f38
Reviewed-on: https://chromium-review.googlesource.com/1087637
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#564757}