commit 4c9a50f64fdf18f2ae3592bf8ca933ec6739ed04
author chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Fri Mar 08 22:10:43 2019
committer Commit Bot <commit-bot@chromium.org> Fri Mar 08 22:10:43 2019
tree 3191347cae0ab96e1cfd8dd3c72b8172685f0a3c
parent 43bb9fdd8e623691e6529987777ebe8a5a2ab365

Roll src/third_party/catapult 5869dbeaf2c4..26a1944e9080 (1 commits)

https://chromium.googlesource.com/catapult.git/+log/5869dbeaf2c4..26a1944e9080


git log 5869dbeaf2c4..26a1944e9080 --date=short --no-merges --format='%ad %ae %s'
2019-03-08 sergiyb@chromium.org Add a workaround to handle incorrect hostname in HTTP_HOST


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

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll

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

Change-Id: Ie5b759ab0277a370e265e59cfcd4d352ccc48c49
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1512415
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#639195}