Commit 557e9774 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/perfetto 2da0d123402a..e92c674abcb9 (5 commits)

https://android.googlesource.com/platform/external/perfetto.git/+log/2da0d123402a..e92c674abcb9


git log 2da0d123402a..e92c674abcb9 --date=short --no-merges --format='%ad %ae %s'
2018-11-22 hjd@google.com Fix merged perfetto trace
2018-11-22 treehugger-gerrit@google.com Merge "SockSend: remove extraneous msg_controllen assignment + micro nit fixups."
2018-11-22 taylori@google.com Add generic ftrace event
2018-11-21 treehugger-gerrit@google.com Merge "Collect ftrace protos into one file per group"
2018-11-21 fmayer@google.com Print PID in parent process.


Created with:
  gclient setdep -r src/third_party/perfetto@e92c674abcb9

The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-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.



BUG=chromium:117471443
TBR=perfetto-bugs@google.com

Change-Id: Icbe137084b670295623061db598b4a99c677ef56
Reviewed-on: https://chromium-review.googlesource.com/c/1348835Reviewed-by: default avatarchromium-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@{#610582}
parent 240ba84a
......@@ -1008,7 +1008,7 @@ deps = {
},
'src/third_party/perfetto':
Var('android_git') + '/platform/external/perfetto.git' + '@' + '2da0d123402a3b93b5f08fdf2fa9ce3d690cdf75',
Var('android_git') + '/platform/external/perfetto.git' + '@' + 'e92c674abcb9a91813118659383335eccfd29db5',
'src/third_party/perl': {
'url': Var('chromium_git') + '/chromium/deps/perl.git' + '@' + 'ac0d98b5cee6c024b0cffeb4f8f45b6fc5ccdb78',
......
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