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

Roll src/third_party/catapult/ 7dc0e251e..9a12da754 (2 commits)

https://chromium.googlesource.com/catapult.git/+log/7dc0e251e9a9..9a12da75442c

$ git log 7dc0e251e..9a12da754 --date=short --no-merges --format='%ad %ae %s'
2018-05-24 wangxianzhu Update reference builds of all channels
2018-05-24 csharrison Fix chown cmd in AndroidPlatformBackend.PushProfile

Created with:
  roll-dep src/third_party/catapult


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

Change-Id: Ia1f0a72544bf46fdf0d3ec443ea6d9959000411b
Reviewed-on: https://chromium-review.googlesource.com/1072149Reviewed-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@{#561654}
parent 4a4e43a7
......@@ -156,7 +156,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': '7dc0e251e9a996fe9007c23022623f466637d238',
'catapult_revision': '9a12da75442c7a1de67849bf33e170d81564cc89',
# 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