Commit d7b531c7 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/chromite 260e87e6956a..4ccba5fc7b22 (2 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/260e87e6956a..4ccba5fc7b22

git log 260e87e6956a..4ccba5fc7b22 --date=short --no-merges --format='%ad %ae %s'
2019-10-15 vapier@chromium.org partial_mock: AddCmdResult: switch to stdout/stderr arg names
2019-10-15 saklein@chromium.org portage_util: Add version validation to chromeos_version.sh call.

Created with:
  gclient setdep -r src/third_party/chromite@4ccba5fc7b22

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/chromite-chromium-autoroll
Please CC chrome-os-gardeners@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel
TBR=chrome-os-gardeners@google.com

Bug: None
Change-Id: I1cc7c13e645d5d594ad71afa2e00b68b027b6feb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862243Reviewed-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@{#706075}
parent dc398ef7
......@@ -862,7 +862,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' + '@' + '260e87e6956a197d49ff83c317b9c33bb1071667',
'url': Var('chromium_git') + '/chromiumos/chromite.git' + '@' + '4ccba5fc7b22f9c9559953bf0ba3907cffb6226c',
'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