New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 627134 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Autotest: Gather Android native crash tombstones

Project Member Reported by bryanlew@chromium.org, Jul 11 2016

Issue description

In Autotest for Android devices using ADBHost, collect native (non-Java crash) tombstones if they are present.  Place these files in the Autotest results.

 
Project Member

Comment 1 by bugdroid1@chromium.org, Jul 15 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/68646b610fad1a951f9d5f6dac839acb0f442bf2

commit 68646b610fad1a951f9d5f6dac839acb0f442bf2
Author: Bryan Lewandowski <bryanlew@google.com>
Date: Tue Jul 12 17:24:57 2016

Autotest: Add Android tombstone collection, and a test for the same.

Other cleanup:
* Modifies the brillo_CrashLogging test to remove any previous crash logs
* Adds OS labels to the control files

BUG= chromium:627134 
TEST=test_droid with Nexus 5 local device
TEST=test_droid against local and remote Brillo devices
TEST=Additional android_CrashLogging test

Change-Id: I5be7ed48c5562ee0fe9174daf3c988eb6374cb1f
Reviewed-on: https://chromium-review.googlesource.com/360021
Commit-Ready: Bryan Lewandowski <bryanlew@google.com>
Tested-by: Bryan Lewandowski <bryanlew@google.com>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>

[modify] https://crrev.com/68646b610fad1a951f9d5f6dac839acb0f442bf2/server/site_tests/brillo_CrashLogging/brillo_CrashLogging.py
[modify] https://crrev.com/68646b610fad1a951f9d5f6dac839acb0f442bf2/server/site_tests/brillo_CrashLogging/control
[add] https://crrev.com/68646b610fad1a951f9d5f6dac839acb0f442bf2/server/site_tests/android_CrashLogging/control
[add] https://crrev.com/68646b610fad1a951f9d5f6dac839acb0f442bf2/server/site_tests/android_CrashLogging/android_CrashLogging.py
[modify] https://crrev.com/68646b610fad1a951f9d5f6dac839acb0f442bf2/server/hosts/adb_host.py

Status: Verified (was: Started)
Project Member

Comment 3 by bugdroid1@chromium.org, 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