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

Roll src/third_party/catapult/ 9cfb34e84..97e6e42e3 (1 commit)

https://chromium.googlesource.com/catapult.git/+log/9cfb34e845c8..97e6e42e3e39

$ git log 9cfb34e84..97e6e42e3 --date=short --no-merges --format='%ad %ae %s'
2017-12-13 simonhatch Dashboard - Small refactor.

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: I12a74d31015cb0d95008e222b8527a1e812c040c
Reviewed-on: https://chromium-review.googlesource.com/826132
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524004}
parent 8d7d05b9
...@@ -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': '9cfb34e845c8308d019a894be8c0926ee8cd3c91', 'catapult_revision': '97e6e42e3e392136a2a67b41768c3e14deec5c3b',
# 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