Ang Li
Ang Li
We actually considered this feature before and decided against it. Maybe the circumstances have changed. Let's discuss offline.
1. this error is not exposed today, bc the adb cmd ret code 0 so it's treated the same as the package is not instrumented. 2. adding nobs for such...
A retry does not mask that exception though. It'll still throw if the device actually crashed etc. This is a pretty standard way to get around adb flakiness in systems...
This is not a high priority thing though as it rarely happens...
Perhaps we could in addition throw a better error for such cases. E.g. if there are lines (except for the first line) that don't start with "^instrumentation:", throw an error...
Flag meaning? This is just to be consistent with how LogPath is set.
Only affects stdout as the title says... Not sure how useful this is though On Jul 31, 2017 8:13 PM, "David T.H. Kao" wrote: > I had meant a command...
Windows CI is broken. Need to fix
This is ready for review