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

Roll src/third_party/catapult/ 3ac7c0f02..dc9404644 (1 commit)

https://chromium.googlesource.com/catapult.git/+log/3ac7c0f0224e..dc9404644cac

$ git log 3ac7c0f02..dc9404644 --date=short --no-merges --format='%ad %ae %s'
2017-12-12 perezju [Devil] Return pid and ppid's as ints

Created with:
  roll-dep src/third_party/catapult


The AutoRoll server is located here: https://catapult-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


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

Change-Id: Ia2653202eea6bfb536af23193632dd042ef35c6f
Reviewed-on: https://chromium-review.googlesource.com/824062
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523743}
parent e0ec8039
...@@ -130,7 +130,7 @@ vars = { ...@@ -130,7 +130,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': '3ac7c0f0224ef18ba45d6cb1017a48ac1d73c5ec', 'catapult_revision': 'dc9404644cac587e0bdc26f4430498f00e8ba3a2',
# 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