Mobile/Testing/05 14 14
From MozillaWiki
Contents
Previous Action Items
- snorp will file a bug for an autophone webapp test
- mcote will try to get more info on eideticker outage
- snorp to lead this meeting for the next 2 weeks (maybe cancel this week?...lots of people away)
Status reports
Dev team
Rel Eng
- bug 1004791 Schedule Android 2.3 crashtests, js-reftests, plain reftests, and m-gl on all trunk trees and make them ride the trains
- bug 1007342 mh and device changes for relocated p3 panda racks
Relops
No new updates. Still waiting for a panda move date to be set.
A Team
- Android 2.2 failure rate: [2.11%]
- last week 2.65%
- Android 2.3 failure rate: [0.86%]
- last week 0.95%
- Android 4.0 failure rate: [22.63%]
- last week 16.59%
- excluding retries 3.87%
Thanks to a contributor, you can now specify date ranges for ouija so you can see historical data or data for periods of other than a week. Unfortunately this seems to have made the queries slower :/
Android 2.3 emulator
- all Android 2.2 functional tests (mochitests, m-gl, robocop, xpcshell, crashtests, js-reftests, plain reftests) are now running on Android 2.3 on trunk, on ix slaves
- To-do/bonus:
- investigate disabled tests, especially robocop - bug 979921
- Android 2.3 armv6 - bug 1005956
- cpp unit tests?
- new avds - bug 989343
Android 4.0 Debug
- gbrown updated/filed new bugs for remaining failures on robocop and mochitest-gl
- recently started running Android 4.0 Debug reftests, xpcshell, cppunittests on Cedar
Autophone
- bug 990601 - Autophone - use adb instead of tcp/ip to control devices landed.
- Planning for move to Mountain View. Will range IT/Netops issues prior to shipment to minimize downtime.
- Short term fixes for Phonedash UI; longer term move to datazilla.
Eideticker
- LG G2X now working again (mostly), Galaxy Nexus still having problems bug 1003507
- Huge weird regression with many checkerboarding tests on LG G2X (bug 1009127), seemingly mostly isolated to not using the low precision buffer (test only) but still interfering with getting good results.
- Some testruns not completing for some reason, tracking letting this happen without interrupting full test suite in bug 1002487