[autotest] Integrate crashlog collection into repair workflow.
When a DUT goes offline before logs are gathered, we lose those
logs if the DUT is re-imaged.
To grab such logs as much as we can, we integrate crashlog
collection into the repair workflow.
BUG=chromium:215160
TEST=./server/autoserv -R -m <DUT ip> -r ~/tmp/repair
CQ-DEPEND=CL:221510
Change-Id: Ifd562bfd539b133381572aeec503d9a3940ab448
Reviewed-on: https://chromium-review.googlesource.com/219999
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Mungyung Ryu <mkryu@google.com>
Tested-by: Mungyung Ryu <mkryu@google.com>
diff --git a/client/cros/constants.py b/client/cros/constants.py
index 2d48683..f6ddd08 100644
--- a/client/cros/constants.py
+++ b/client/cros/constants.py
@@ -33,6 +33,7 @@
# LOGS to collect from DUTs
LOG_CONSOLE_RAMOOPS = '/dev/pstore/console-ramoops'
LOG_I915_ERROR_STATE = '/sys/kernel/debug/dri/0/i915_error_state'
+PRIOR_LOGS_DIR = '/mnt/stateful_partition/unencrypted/prior_logs'
CREDENTIALS = {
'$mockowner': ['mockowner.test.account@gmail.com', 'perfsmurf'],