Move Android marionette tests to Android 7.0 x86_64
Categories
(Remote Protocol :: Marionette, defect, P3)
Tracking
(firefox67 fixed)
Tracking | Status | |
---|---|---|
firefox67 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
(Depends on 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
Assignee | ||
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
Assignee | ||
Comment 3•6 years ago
|
||
Comment 4•6 years ago
|
||
Assignee | ||
Comment 5•6 years ago
|
||
Assignee | ||
Comment 6•6 years ago
|
||
Updated•6 years ago
|
Comment 7•6 years ago
|
||
Geoff, does something else still block us, or can we proceed with this bug? Would be great to see us moving away from the old emulator.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 8•6 years ago
|
||
There are some test failures in the new environment. I reported one with an obvious fix, but I don't have much time to look into the others just now. Otherwise, I think we are ready to move.
Comment 9•6 years ago
|
||
I filed two additional bugs for those remaining two cases. I think that we should be able to switch over soon.
Assignee | ||
Comment 10•6 years ago
|
||
I still see frequent "Port 127.0.0.1:2828 is unavailable.":
Most of those go away if we run in more chunks:
I'd like to figure out what is causing that.
Comment 11•6 years ago
|
||
Good question. At least the Android logcat isn't that particular helpful. I wasn't able to find anything related to this connection problem. Could it be some instability with adb and port forwarding? Maybe that just drops at some random interval?
Comment 12•6 years ago
|
||
So the crashes (bug 1527254) will be fixed soon. Geoff, could you push another try build once it has been done? Lets see what's remaining.
Assignee | ||
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
Note that I commented on the remaining blocking bugs for making this transition real. All of them look like issues with adb or the emulator but not the Marionette tests. When I run the tests locally in a x86-7.0 emulator it works all fine, and no failures are present.
Assignee | ||
Comment 15•6 years ago
|
||
Comment 16•6 years ago
|
||
With the recent try push only the screen orientation failures are blocking us from moving over to the x86_86 emulator. I will try to get this done today.
Comment 17•6 years ago
|
||
Depends on D21358
Updated•6 years ago
|
Comment 18•6 years ago
|
||
Comment on attachment 9047040 [details]
Bug 1500509 - Move marionette tests to Android 7.0 x86_64
Sorry, moz-phab uploaded this temporarily applied patch. I don't want to steal Geoff's work.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 19•6 years ago
|
||
Comment 20•6 years ago
|
||
Comment 21•6 years ago
|
||
bugherder |
Assignee | ||
Comment 22•6 years ago
|
||
Checking a few pushes before/after this change, I estimate Android 4.3 Mn was taking about 300 minutes of aws time per push (all chunks on opt and debug combined) and Android 7.0 is taking about 20 minutes of packet.net time per push.
Comment 23•6 years ago
|
||
I noticed that too, which is an amazing improvement for resource usage and costs. It's great to see that this is done now.
Updated•6 years ago
|
Updated•2 years ago
|
Description
•