Intermittent ValueError: invalid literal for int() with base 10: '' for adb_android.py
Categories
(Testing :: General, defect, P2)
Tracking
(firefox67 fixed)
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: gbrown)
Details
(Keywords: intermittent-failure)
Attachments
(1 file)
|
1.36 KB,
patch
|
bc
:
review+
|
Details | Diff | Splinter Review |
Comment 1•7 years ago
|
||
Updated•7 years ago
|
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 9•6 years ago
|
||
:gbrown, should this be an auto retry? from an unfamiliar point of view this looks like we cannot connect to the emulator.
| Assignee | ||
Comment 10•6 years ago
|
||
We have connected to the emulator and run adb commands earlier, but requesting the api level fails ("getprop ro.build.version.sdk" returns ''). Maybe boot hasn't fully completed, somehow? Let's catch the ValueError, maybe retry in adb.py, and fail with an ADBError if the condition persists. I'll put together a simple patch.
| Assignee | ||
Comment 11•6 years ago
|
||
I do not know if this will be effective, but I think it is worth a try.
(This version of the patch has corrected for the f8 error in the try push.)
Comment 12•6 years ago
|
||
| Assignee | ||
Comment 13•6 years ago
|
||
I am open to adding a comment or using a different error, if you prefer.
There is an existing use of ADBTimeoutError just a little earlier, at
which was my inspiration.
Comment 14•6 years ago
|
||
Good point. I missed that. /nick Roseanne Roseannadanna: Never mind.
Comment 15•6 years ago
|
||
Comment 16•6 years ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
Description
•