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

Roll src/third_party/catapult 34f0d7e2e45f..3836c556c4c6 (1 commits)

https://chromium.googlesource.com/catapult.git/+log/34f0d7e2e45f..3836c556c4c6


git log 34f0d7e2e45f..3836c556c4c6 --date=short --no-merges --format='%ad %ae %s'
2018-07-02 pasko@chromium.org androidStartupMetric: Allow multiple FCP events


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

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

Change-Id: I10d9051ea1022d1a0b1cf64eddf04cd9cbc79113
Reviewed-on: https://chromium-review.googlesource.com/1122436Reviewed-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@{#571883}
parent dc3698a4
......@@ -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': '34f0d7e2e45f3c8796b6f37fd99ea1117f6218b2',
'catapult_revision': '3836c556c4c64a3820bf0656bf2b1cfcf8dbb16a',
# 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