Autotest: Gather Android native crash tombstones |
||
Issue descriptionIn Autotest for Android devices using ADBHost, collect native (non-Java crash) tombstones if they are present. Place these files in the Autotest results.
,
Jul 15 2016
,
Jul 26 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/8c96bb2b1eccf3bbfff88efb7cbed5bcf78b09c9 commit 8c96bb2b1eccf3bbfff88efb7cbed5bcf78b09c9 Author: Bryan Lewandowski <bryanlew@google.com> Date: Tue Jul 19 19:56:03 2016 Reenable logging, warn on logging failure. Reenables native crash logging, and considers the inability to enable crash logging as a warning rather than an error. This is important because the provision operation calls job_start(), and depending on the preexisting image on the DUT, the attempt to enable logging will fail. Note that job_start() is called again to start the test case, so logging will be enabled once the device is provisioned with the image under test. BUG= chromium:623743 BUG= chromium:627134 TEST=Local test_droid on Brillo: android_DummyTest brillo_CrashLogging TEST=Local test_droid on Android: android_DummyTest android_CrashLogging TEST=Lab test_droid on Brillo: android_DummyTest brillo_CrashLogging TEST=Guado MobLab on Brillo: android_DummyTest brillo_CrashLogging Change-Id: I1da04f7f2c7c5133ea7befaf152afb4e2166f406 Reviewed-on: https://chromium-review.googlesource.com/362611 Commit-Ready: Bryan Lewandowski <bryanlew@google.com> Tested-by: Bryan Lewandowski <bryanlew@google.com> Reviewed-by: Simran Basi <sbasi@chromium.org> [modify] https://crrev.com/8c96bb2b1eccf3bbfff88efb7cbed5bcf78b09c9/server/hosts/adb_host.py |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Jul 15 2016