[Predator] port stacktrace parsing for ClusterFuzz |
|||||||
Issue descriptionIf we are gonna to process the raw stack trace on Findit side as planned, we need to port the logic over to Findit app. If we decide to do that on the client side (ClusterFuzz, Fracas, Chromecrash), we need to make a change on ClusterFuzz side. In the later case, a stack trace is a list of callstacks, a callstack is a list of frames, a frame has a file path and a line number. A stack trace and a callstack could have a list of key-value attributes to include the pid, process name, etc.
,
May 26 2016
,
Nov 30 2016
,
Nov 30 2016
,
Dec 1 2016
,
Dec 1 2016
,
Jan 3 2017
Cls that implement this - Rewrote and ported all clusterfuzz filters - https://codereview.chromium.org/2588133003. Refactored ChromeCrash parser. - https://codereview.chromium.org/2593383002 flag manager - https://codereview.chromium.org/2593093003 clusterfuzz parsers for review - https://codereview.chromium.org/2593593003.
,
Jan 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra.git/+/dcecde7f28e429a1f24053e679136d00c2d712e9 commit dcecde7f28e429a1f24053e679136d00c2d712e9 Author: katesonia <katesonia@chromium.org> Date: Wed Jan 04 18:01:32 2017 [Predator] Pass flags to callstack detector and fix nit. A minor bug fixing - passing flags to callstack detector in cluterfuzz parser Fix a remaining nit. BUG= 605360 TBR=stgao@chromium.org Review-Url: https://codereview.chromium.org/2610763002 [modify] https://crrev.com/dcecde7f28e429a1f24053e679136d00c2d712e9/appengine/findit/crash/clusterfuzz_parser.py [modify] https://crrev.com/dcecde7f28e429a1f24053e679136d00c2d712e9/appengine/findit/crash/flag_manager.py [modify] https://crrev.com/dcecde7f28e429a1f24053e679136d00c2d712e9/appengine/findit/crash/test/flag_manager_test.py
,
Jan 24 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by st...@chromium.org
, Apr 21 2016