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

Roll src/third_party/catapult 6cef7cac8d71..f62079a0f9e5 (1 commits)

https://chromium.googlesource.com/catapult.git/+log/6cef7cac8d71..f62079a0f9e5


git log 6cef7cac8d71..f62079a0f9e5 --date=short --no-merges --format='%ad %ae %s'
2018-08-17 chiniforooshan@chromium.org Telemetry: queueing_durations in TBMv2


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

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

Change-Id: I575568b7cb1ec5dbf3d61a8b2427a055eb40dc0c
Reviewed-on: https://chromium-review.googlesource.com/1180002Reviewed-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@{#584212}
parent da8490d6
......@@ -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': '6cef7cac8d71a9f40f454c922a0579fa36424150',
'catapult_revision': 'f62079a0f9e5b7c9e95af4e12adf86675cf57e74',
# 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