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

Roll src/third_party/catapult/ 31cacbe5d..3f41f93f9 (2 commits)

https://chromium.googlesource.com/catapult.git/+log/31cacbe5d6d2..3f41f93f9154

$ git log 31cacbe5d..3f41f93f9 --date=short --no-merges --format='%ad %ae %s'
2017-09-29 benjhayden Add tr.v.d.RelatedNameMap to TBMv2.
2017-10-02 benjhayden Fix uses of /deep/ in trace viewer.

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: I53747eaddc824d1f5be2e0e2c1aafb093a4d3272
Reviewed-on: https://chromium-review.googlesource.com/696127
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#505909}
parent ac35e536
...@@ -101,7 +101,7 @@ vars = { ...@@ -101,7 +101,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': '31cacbe5d6d2d4d9cdf1cc6b4c793b62add3c5d0', 'catapult_revision': '3f41f93f9154b9acb9e5ff9347827355a27341e9',
# 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