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

Roll src/third_party/depot_tools 6a1d77869d77..b2b51418596e (2 commits)

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/6a1d77869d77..b2b51418596e

git log 6a1d77869d77..b2b51418596e --date=short --no-merges --format='%ad %ae %s'
2019-10-10 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).
2019-10-10 dbeam@chromium.org git-cl: add --fixed / -x option to upload

Created with:
  gclient setdep -r src/third_party/depot_tools@b2b51418596e

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/depot-tools-chromium-autoroll
Please CC agable@chromium.org 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

TBR=agable@chromium.org

Bug: None
Change-Id: I6194a05084f3dd9fe62ba8d4bc8e86cc98385afc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1854551Reviewed-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@{#704916}
parent 47ccc9c4
......@@ -887,7 +887,7 @@ deps = {
},
'src/third_party/depot_tools':
Var('chromium_git') + '/chromium/tools/depot_tools.git' + '@' + '6a1d77869d77b61189247ce8b47ac9d86684a6c2',
Var('chromium_git') + '/chromium/tools/depot_tools.git' + '@' + 'b2b51418596ec5465a49405a36b6dee55c42488d',
'src/third_party/devtools-node-modules':
Var('chromium_git') + '/external/github.com/ChromeDevTools/devtools-node-modules' + '@' + Var('devtools_node_modules_revision'),
......
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