Autotest: add Android logcat log to Autotest results |
|||||
Issue descriptionAndroid produces a log in the form of logcat. Capture this log in Autotest when running tests, and add it to the test results.
,
May 26 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/f21ef531bc634830a043d6b09e2976b571b56a71 commit f21ef531bc634830a043d6b09e2976b571b56a71 Author: Bryan Lewandowski <bryanlew@google.com> Date: Tue May 10 18:21:04 2016 Enable logcat logging for adb_host. 1. Perform an approximate sync of host and server clocks so that logcat and Autotest server/test-runner logs can be compared/matched. 2. Save ADB device's logcat as 'logcat.log' in the results-#-suiteName directory. The entire logcat is included since there are often boot-time errors which manifest as a test failure much later, for example, a daemon crashing. BUG= chromium:610699 TEST=L and M devices (for time-set function) TEST=test_droid (on appropriate internal whitelisted targets) Change-Id: Ib4b9a0779e3c781140b6a589fc291863e5be44b3 Reviewed-on: https://chromium-review.googlesource.com/343911 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/f21ef531bc634830a043d6b09e2976b571b56a71/server/hosts/adb_host.py
,
May 26 2016
,
May 26 2016
,
May 26 2016
I might see a bug related to this CL: http://dshi1.mtv.corp.google.com/results/1048-debug_user/100.96.51.111/debug/autoserv.DEBUG adb -s ZX1G22K3SQ logcat -v time -d > "/usr/local/autotest/results/1048-debug_user/100.96.51.111/logcat.log" testbed does not have fold /usr/local/autotest/results/1048-debug_user/100.96.51.111/.
,
May 31 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/0f3f011ce18fa9c547cd5da40170742ae9ad0bf6 commit 0f3f011ce18fa9c547cd5da40170742ae9ad0bf6 Author: Bryan Lewandowski <bryanlew@google.com> Date: Fri May 27 22:17:19 2016 Enable logcat logging for adb_host. 1. Perform an approximate sync of host and server clocks so that logcat and Autotest server/test-runner logs can be compared/matched. 2. Save ADB device's logcat as 'logcat.log' in the test job's results directory. The entire logcat is included since there are often boot-time errors which manifest as a test failure much later, for example, a daemon crashing. BUG= chromium:610699 TEST=L and M devices (for time-set function) TEST=test_droid (on appropriate internal whitelisted targets) TEST=test_droid on local and remote teststations Change-Id: Ib7a0a7cf615fdc12ae69f90578bd3fe5160f6a55 Reviewed-on: https://chromium-review.googlesource.com/347989 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/0f3f011ce18fa9c547cd5da40170742ae9ad0bf6/server/hosts/adb_host.py
,
Jun 27 2016
Resolved (with follow-up CLs), closed. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bryanlew@chromium.org
, May 10 2016