Observed while dogfooding: doctor on a machine with a wedged adb reports:
! device-android: Android device inventory could not be read: adb timed out after 10000ms
hint: Retry with --debug and inspect diagnostics log for details.
The actionable move for an adb timeout is adb kill-server && adb start-server (or checking adb devices directly) — retrying with --debug will time out identically. #1067's classifier keys on stderr text and covers device offline / INSTALL_FAILED_*, but a timeout has no stderr to classify, so it falls through to the generic hint.
Expectation: the adb executor's timeout path (and doctor's inventory check) should carry a timeout-specific hint suggesting the adb server restart. Fits naturally as another matcher/branch in #1067's centralized classification once it merges.
Observed while dogfooding:
doctoron a machine with a wedged adb reports:The actionable move for an adb timeout is
adb kill-server && adb start-server(or checkingadb devicesdirectly) — retrying with --debug will time out identically. #1067's classifier keys on stderr text and coversdevice offline/INSTALL_FAILED_*, but a timeout has no stderr to classify, so it falls through to the generic hint.Expectation: the adb executor's timeout path (and doctor's inventory check) should carry a timeout-specific hint suggesting the adb server restart. Fits naturally as another matcher/branch in #1067's centralized classification once it merges.