Commit 6da17b79 authored by catapult-chromium-autoroll's avatar catapult-chromium-autoroll Committed by Commit Bot

Roll src/third_party/catapult ca2b32c84463..d269b0e87d1e (1 commits)

https://chromium.googlesource.com/catapult.git/+log/ca2b32c84463..d269b0e87d1e


git log ca2b32c84463..d269b0e87d1e --date=short --no-merges --format='%ad %ae %s'
2018-07-24 anthonyalridge@google.com Initial files for plotting a simple line graph.


Created with:
  gclient setdep -r src/third_party/catapult@d269b0e87d1e

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=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel

BUG=chromium:866423
TBR=sullivan@chromium.org

Change-Id: I6d810da1512eea82945a307c7dc749e8b733e3b5
Reviewed-on: https://chromium-review.googlesource.com/1147958Reviewed-by: default avatarcatapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#577602}
parent d18ad7c1
......@@ -165,7 +165,7 @@ vars = {
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling catapult
# and whatever else without interference from each other.
'catapult_revision': 'ca2b32c844637750526112f1af7fbb28b17a8f83',
'catapult_revision': 'd269b0e87d1ef7db8336af727f4215f73ed0f7b8',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling libFuzzer
# 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