Commit ea556962 authored by Chromite Chromium Autoroll's avatar Chromite Chromium Autoroll Committed by Commit Bot

Roll src/third_party/chromite 3fff4ff38701..3e03eba0a7e2 (4 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/3fff4ff38701..3e03eba0a7e2


git log 3fff4ff38701..3e03eba0a7e2 --date=short --no-merges --format='%ad %ae %s'
2018-07-27 tbrindus@chromium.org cros_generate_update_payload: Convert to chromite
2018-07-27 dgarrett@google.com chromeos_config: Checkin luci-scheduler.cfg.
2018-07-27 chirantan@chromium.org cros_setup_toolchains: Add llvm-libunwind as an extra package
2018-07-27 vadimsh@chromium.org cipd: Bump cipd client version to the one that understands SHA256 hashes.


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

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: I23aa03b0168fe1dd0959748474fe74c7f5aa8632
Reviewed-on: https://chromium-review.googlesource.com/1153509Reviewed-by: default avatarChromite 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@{#578805}
parent be677c94
......@@ -539,7 +539,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' + '@' + '3fff4ff387013909c6730744773e97f991444f54',
'url': Var('chromium_git') + '/chromiumos/chromite.git' + '@' + '3e03eba0a7e24ca8ca0a0d616e4801b38a2260e7',
'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