Roll src/third_party/catapult e3b12b3e7d98..fa74d9840634 (2 commits)

https://chromium.googlesource.com/catapult.git/+log/e3b12b3e7d98..fa74d9840634


git log e3b12b3e7d98..fa74d9840634 --date=short --no-merges --format='%ad %ae %s'
2018-06-22 perezju@chromium.org [Telemetry] Should not "warn" when computing TBM
2018-06-22 perezju@chromium.org [Telemetry] Do not raise on missing devtools clients for clock sync


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

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

Change-Id: I228ac2a4d7ae2ad4ae535d3dd69fe390b0c73c44
Reviewed-on: https://chromium-review.googlesource.com/1112119Reviewed-by: catapult-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@{#569731}

DEPS

@@ -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': 'e3b12b3e7d9897ed96788fa1eb985fff7b1e85ce',
+  'catapult_revision': 'fa74d98406348d49f21f88bf06eed777e362c08f',
   # Three lines of non-changing comments so that
   # the commit queue can handle CLs rolling libFuzzer
   # and whatever else without interference from each other.