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

Roll src/third_party/catapult 134364159fa8..2acd8e0354e2 (1 commits)

https://chromium.googlesource.com/catapult.git/+log/134364159fa8..2acd8e0354e2


git log 134364159fa8..2acd8e0354e2 --date=short --no-merges --format='%ad %ae %s'
2018-08-01 oysteine@chromium.org Removed an old restriction on timestamp ordering of trace events


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

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: I5830d896d7a62027b4b30950becf5f87b745d865
Reviewed-on: https://chromium-review.googlesource.com/1159701Reviewed-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@{#580026}
parent 4ec98692
......@@ -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': '134364159fa81d86a806d5b3c0ec70e88cec1fd9',
'catapult_revision': '2acd8e0354e258f1322d6426c6e3689b398b85f6',
# 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