Roll src/third_party/catapult/ b90b97cf8..e490e96cd (2 commits)

https://chromium.googlesource.com/catapult.git/+log/b90b97cf8dec..e490e96cd7f3

$ git log b90b97cf8..e490e96cd --date=short --no-merges --format='%ad %ae %s'
2018-03-08 dtu [dashboard] Add api_auth.Email() function.
2018-03-08 dtu [pinpoint] Delete extraneous patch argument when trying a patch.

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.


TBR=sullivan@chromium.org

Change-Id: I5e184099e83aa7a3aa66bbd528b9a7e36afaa948
Reviewed-on: https://chromium-review.googlesource.com/957311
Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: default avatarcatapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#542206}
parent 5dda5e51
...@@ -135,7 +135,7 @@ vars = { ...@@ -135,7 +135,7 @@ vars = {
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling catapult # the commit queue can handle CLs rolling catapult
# and whatever else without interference from each other. # and whatever else without interference from each other.
'catapult_revision': 'b90b97cf8dec1060b14197b68a7c862bab7e4ed5', 'catapult_revision': 'e490e96cd7f3c0cc32ecbb6faf25a88b3ca64ec4',
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling libFuzzer # the commit queue can handle CLs rolling libFuzzer
# and whatever else without interference from each other. # 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