Commit 8d9c0f04 authored by chromite-chromium-autoroll's avatar chromite-chromium-autoroll Committed by Commit Bot

Roll src/third_party/chromite/ 07dfd789c..fdd7e08cd (5 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/07dfd789cb28..fdd7e08cde5d

$ git log 07dfd789c..fdd7e08cd --date=short --no-merges --format='%ad %ae %s'
2018-05-21 yunlian cros_gdb: support simple chrome
2018-05-21 bmgordon chroot_lib: Remove ChrootManager
2018-05-21 ayatane sysmon: Refactor prod_metrics: Remove _LoggingSink
2018-05-21 ayatane sysmon: Refactor prod_metrics: Remove _AtestSource
2018-05-21 ayatane sysmon: Refactor prod_metrics: Remove _ProdHostReporter

Created with:
  roll-dep src/third_party/chromite
BUG=chromium:843275,chromium:845174,chromium:None,chromium:None,chromium:None


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.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I32201b36652a22d6f98c4c470ae1319206badc92
Reviewed-on: https://chromium-review.googlesource.com/1069979
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: default avatarChromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#560986}
parent 1ce3f1be
......@@ -498,7 +498,7 @@ deps = {
# Build tools for Chrome OS. Note: This depends on third_party/pyelftools.
'src/third_party/chromite': {
'url': Var('chromium_git') + '/chromiumos/chromite.git' + '@' + '07dfd789cb28b055bfff16f21e3f635fc3ef9c90',
'url': Var('chromium_git') + '/chromiumos/chromite.git' + '@' + 'fdd7e08cde5d02ec43ff91e5a3a6a2fd22035269',
'condition': 'checkout_linux',
},
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment