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

Roll src/third_party/catapult/ 861d4a174..c294424b5 (1 commit)

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/861d4a174136..c294424b587e

$ git log 861d4a174..c294424b5 --date=short --no-merges --format='%ad %ae %s'
2017-06-01 perezju [systrace] Use large_output=True when collecting atrace data

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: Id9541437d4ef441e5ab4c5f5c58eb677dc134623
Reviewed-on: https://chromium-review.googlesource.com/521422
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#476349}
parent 353eaeaa
...@@ -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': '861d4a17413608f1a3f93f3dc503c7d2f3305cfa', 'catapult_revision': 'c294424b587eb0a331556f215cacb5b22e066438',
# 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