Commit de4c4327 authored by catapult-deps-roller@chromium.org's avatar catapult-deps-roller@chromium.org Committed by Commit Bot

Roll src/third_party/catapult/ 1c3f4b921..2b7090e93 (1 commit)

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/1c3f4b921788..2b7090e93566

$ git log 1c3f4b921..2b7090e93 --date=short --no-merges --format='%ad %ae %s'
2017-05-01 aschulman [Devil] Added Cherry Mobile One USB charging control commands.

Created with:
  roll-dep src/third_party/catapult


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

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: Ie1ee49db40e87f1ff157a8dd2c55322ab1f9c63c
Reviewed-on: https://chromium-review.googlesource.com/491526
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#468400}
parent 4d46c8d9
...@@ -96,7 +96,7 @@ vars = { ...@@ -96,7 +96,7 @@ vars = {
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling catapult # the commit queue can handle CLs rolling catapult
# and whatever else without interference from each other. # and whatever else without interference from each other.
'catapult_revision': '1c3f4b92178893dfd439e64740a3aa334fdac21f', 'catapult_revision': '2b7090e93566d7874d3079c2b8f2341e8fb1d201',
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling libFuzzer # the commit queue can handle CLs rolling libFuzzer
# and whatever else without interference from each other. # and whatever else without interference from each other.
......
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