Commit 1709c286 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/chromite 44bef83f2be0..9ace67b95f5c (6 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/44bef83f2be0..9ace67b95f5c


git log 44bef83f2be0..9ace67b95f5c --date=short --no-merges --format='%ad %ae %s'
2018-11-21 dburger@chromium.org remove unused GetSlaveBuildMessages call
2018-11-21 lamontjones@chromium.org signing: Add KeyPair.ParsePrivateKeyFilename
2018-11-20 chrome-bot@chromium.org Update config settings by config-updater.
2018-11-20 gmeinke@chromium.org lakitu-gpu: mark as experimental
2018-11-20 chrome-bot@chromium.org Update config settings by config-updater.
2018-11-20 jemele@google.com Remove deprecated loonix boards


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

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.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I945a20b864e9e25b77e8236c853e0bed8ab7a4fb
Reviewed-on: https://chromium-review.googlesource.com/c/1345929Reviewed-by: default avatarchromium-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@{#610016}
parent b4088a97
......@@ -646,7 +646,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' + '@' + '44bef83f2be0f01d410f436c519da2987cca5747',
'url': Var('chromium_git') + '/chromiumos/chromite.git' + '@' + '9ace67b95f5cd3023174a016fae8a0805375d16b',
'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