FAIL: adb is not ready in 60 seconds. |
|||||||
Issue descriptionThis doesn't happen often, but the root cause is not known: https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_minnie-cheets-chrome-pfq/builds/477 Let's start by adding more logging.
,
Aug 2 2016
Also seen in ContainerSmokeTest ( issue 633664 , duplicated)
,
Aug 2 2016
https://chromium-review.googlesource.com/#/c/364383/ Should add some logging to diagnose this.
,
Aug 3 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/b6168e5d23e8916922564de8823f0cd915260c53 commit b6168e5d23e8916922564de8823f0cd915260c53 Author: Luis Hector Chavez <lhchavez@google.com> Date: Fri Jul 29 19:37:38 2016 [Autotest]: Save Android dumpstate on ARC tests This change triggers the execution of Android's dumpstate upon test termination and saves its output to /var/log/arc-dumpstate.log. This will add 12-20s seconds to every ArcTest and collect an extra 4MB worth of logs. BUG= chromium:632836 TEST=/var/log/arc-dumpstate.log is present after an ArcTest. Change-Id: I11702b49a2e4e2e0884c1ce8dcedce98f98486a3 Reviewed-on: https://chromium-review.googlesource.com/364383 Commit-Ready: Luis Hector Chavez <lhchavez@google.com> Tested-by: Luis Hector Chavez <lhchavez@google.com> Reviewed-by: Junichi Uekawa <uekawa@chromium.org> Reviewed-by: Ricky Zhou <rickyz@chromium.org> [modify] https://crrev.com/b6168e5d23e8916922564de8823f0cd915260c53/client/common_lib/cros/arc_util.py
,
Dec 5 2016
We have since stabilized the ARC-related PFQ tests, so marking this as fixed.
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Aug 3 2017
Closing. Please reopen it if its not fixed. Thanks! |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by steve...@chromium.org
, Aug 2 2016