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

Roll src/third_party/catapult f153b902bec3..a2cee4816d7b (1 commits)

https://chromium.googlesource.com/catapult.git/+log/f153b902bec3..a2cee4816d7b


git log f153b902bec3..a2cee4816d7b --date=short --no-merges --format='%ad %ae %s'
2018-06-20 perezju@chromium.org [Telemetry] Disable flaky tests on mac10.10


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

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: I658c7b1910c92c4c900861f846404574d1891f85
Reviewed-on: https://chromium-review.googlesource.com/1107599Reviewed-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@{#568813}
parent ba9df781
......@@ -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': 'f153b902bec3811dd5faa9e807240b059e7bbc8c',
'catapult_revision': 'a2cee4816d7bfcc19abd3653e455a745cff1e9b4',
# 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