Symbolized stdout should retain unsymbolized log |
||
Issue descriptionSeeing several cases where the only failure log for instrumentation test failures is the output from the stack script: Searching for native crashes in: /b/swarming/w/itxzeCQ7/tmpUVyi4Q Unknown Android release, consider passing --packed-lib. Reading Android symbols from: /b/swarming/w/ir Searching for Chrome symbols from within: /b/swarming/w/ir/out/Release/lib.unstripped:/b/swarming/w/ir/out/Release/lib:/b/swarming/w/ir/out/Release https://luci-milo.appspot.com/buildbot/chromium.linux/Android%20Tests/45235 We should try just appending the symbolized output to the unsymbolized stack.
,
Aug 28 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f224fff0b36b75e9e67ec4a800f88a314f8cb476 commit f224fff0b36b75e9e67ec4a800f88a314f8cb476 Author: Zhiling Huang <hzl@chromium.org> Date: Mon Aug 28 21:04:56 2017 Print out unsymbolized stack together with symbolized stack. Previously we only printed out symbolized stack, which may cause information to be lost (those that cannot be symbolized in the log will not appear in symbolized stack). In this cl, I print out unsymbolized stack first, then symbolized stack, to make sure no info is lost. Bug: 759617 Change-Id: I65c7406ac233a2aac4d28fd10359f91cf56375c0 Reviewed-on: https://chromium-review.googlesource.com/638859 Commit-Queue: Zhiling Huang <hzl@chromium.org> Reviewed-by: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#497872} [modify] https://crrev.com/f224fff0b36b75e9e67ec4a800f88a314f8cb476/build/android/pylib/instrumentation/instrumentation_test_instance.py
,
Aug 30
|
||
►
Sign in to add a comment |
||
Comment 1 by hzl@chromium.org
, Aug 28 2017