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

Roll src/third_party/catapult/ 24e36dadf..121ef2b4a (1 commit)

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/24e36dadf5b1..121ef2b4a8c6

$ git log 24e36dadf..121ef2b4a --date=short --no-merges --format='%ad %ae %s'
2017-04-19 rnephew [Telemetry] Get rid of old debugging information.

Created with:
  roll-dep src/third_party/catapult
BUG=667470


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: I20439992b215d7734dad275d7a9ebe0cb27b3d11
Reviewed-on: https://chromium-review.googlesource.com/481900
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#465667}
parent cc2c2010
...@@ -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': '24e36dadf5b1aff6cebffa55b476cd7ef64eba0a', 'catapult_revision': '121ef2b4a8c6adbb65df758521fb4f80e78d1d2e',
# 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