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

Roll src/third_party/catapult 5ecb02850aa4..c5ef6d834a15 (1 commits)

https://chromium.googlesource.com/catapult.git/+log/5ecb02850aa4..c5ef6d834a15


git log 5ecb02850aa4..c5ef6d834a15 --date=short --no-merges --format='%ad %ae %s'
2018-06-19 treib@chromium.org Disable flaky ActionRunnerTest.testWait on Mac


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

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:853865
TBR=sullivan@chromium.org

Change-Id: I57b9ff27d91409e0c79cf2dde0ee583fa5662693
Reviewed-on: https://chromium-review.googlesource.com/1106019Reviewed-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@{#568441}
parent a0ac1c26
......@@ -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': '5ecb02850aa4d8eefd1c84626a6ad15f47f58048',
'catapult_revision': 'c5ef6d834a158822a50c67dc117835b28b32be73',
# 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