symbolize native crash stacks on android bots |
|||||||
Issue descriptionDidn't find an existing bug, so filing new one. Since switching to swarming everywhere, we've lost the step that runs the symbolization script through the logcat. So I think first step is to make sure this happens on swarming as well, because this saves a *lot* of developer time when their CL introduces a crash. This has happened to me many times. Second step is to make the symbolized stack, or in general, the logcat corresponding to a test easier to find. There are very few people who knows what to do when an android test crashes. crbug.com/448050 has a bunch of info about this for the old bot config
,
Nov 7 2016
This is related to the work that hzl is doing in issue 631213 , so assigning to him for now.
,
Dec 19 2016
,
Jan 6 2017
Issue 549348 has been merged into this issue.
,
Jan 27 2017
ping, I get asked about debugging android failures maybe once per week, and this would help a *lot* when it's actually a native crash
,
Jun 1 2017
What's the status here?
,
Jun 1 2017
It looks like there's still work ongoing in bug 631213 , but in the meantime, you can use the following optional/non-CQ trybots to fetch symbolized crash dumps the way you used to: https://build.chromium.org/p/tryserver.chromium.android/builders/android_unswarmed_n5_rel https://build.chromium.org/p/tryserver.chromium.android/builders/android_unswarmed_n5x_rel Those are a temporary work-around while we work on porting the necessary logic to swarming.
,
Jun 2 2017
Thanks. I had tried that, but my particular crash doesn't repro on the unswarmed bots for some reason. (I have obtained a stack by now, but it took me a lot of work.) The bot you mention having ongoing work is only about instrumentatino tests, not gtest, from what I understand.
,
Aug 22 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/433f98bc954b5c375337a67998e971393878a0d3 commit 433f98bc954b5c375337a67998e971393878a0d3 Author: Zhiling Huang <hzl@chromium.org> Date: Tue Aug 22 23:16:21 2017 [Android] Symbolize the stack trace in logcat. Previously the stack trace inside logcat is not symbolized, making it difficult to debug. This cl creates a logcat_symbolizer that symbolizes the stack trace in a logcat with the new stack_symbolizer and replaces the unsymbolized stack trace in logcat with the symbolized stace trace. The logcat_symbolizer will be called when we record logcat during test runs. Bug: 657040 Change-Id: Ie6c762a088a8e32dbb7095eb661d3a8a25918baf Reviewed-on: https://chromium-review.googlesource.com/592492 Commit-Queue: Zhiling Huang <hzl@chromium.org> Reviewed-by: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#496496} [add] https://crrev.com/433f98bc954b5c375337a67998e971393878a0d3/build/android/pylib/android/logcat_symbolizer.py
,
Dec 4 2017
Moving Infra>Client>Android -> Infra>Client>Chrome+OS=Android
,
Dec 4 2017
,
Aug 30
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by boliu@chromium.org
, Nov 7 2016