Roll src/third_party/catapult/ 6377613b1..0e201cdd0 (1 commit).

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/6377613b1a29..0e201cdd06ed

$ git log 6377613b1..0e201cdd0 --date=short --no-merges --format='%ad %ae %s'
2017-01-12 hjd Hopefully this will make it easier for people coming to the memory infra UI for the first time to understand what is happening.

BUG=663353

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2622363004
Cr-Commit-Position: refs/heads/master@{#443218}

DEPS

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