Mobile/Testing/04 15 15
From MozillaWiki
Contents
Previous Action Items
Status reports
Dev team
Rel Eng
- Android 4.3 jobs are enabled on try but hidden because the jobs had to be renamed. Jobs will be renamed on next reconfig and opt jobs unhidden. bug 1133833
Relops
A Team
- android-2-3-armv7-api9 Total failure rate: [0.72%]
- last week 0.81%
- total failure excluding retries 0.61%
- android-4-0-armv7-api11 Total failure rate: [15.4%]
- last week 11.71%
- total failure excluding retries 0.75%
Data fetched for: 2015-04-08 15:07 — 2015-04-14 20:22
- [gbrown] bug 1120727 Add mach commands for mochitest-plain and mochitest-chrome on Android
Autophone
- FIXED bug 1153913 Autophone - 2015-04-12 deployment.
- ADDED bug 1153855 Autophone - tracking bug for unit test failures
- WORKING bug 1151439 Autophone - enable Mochitest Media, Reftest ogg and webm video tests.
- Enabled Mm mochitest-media tests. No consensus on reftest video tests. Disabled Mdb, Mdm, Msk, Mtw on all branches. When bug 1153992 is fixed, will re-enable these on try only.
- WORKING bug 1153992 Autophone - allow test manifest to include multiple sections per test script.
- Need this in order to better partition tests across devices and repos which is required for the nytimes and remote tests. Testing an approach locally.
- WORKING bug 1065599 Autophone - audit/update Fennec preferences.
- Waiting on feedback from mfinkle.
- WORKING bug 1150111 Autophone - Add nytimes to page load tests
- Have page updated in ep1 to support Autophone and have tested locally.
- Depends on bug 1153992.
- WORKING bug 1152392 Autophone - webappstartup should detect and use the proper profile.
- Initial attempts to get webapp to use my profile have failed, but I'm not out of options yet.
- WORKING bug 1151882 - Autophone - re-enable remote tests
- Depends on bug 1153992.
Eideticker
- Close to resolving issues and getting this thing running again. Machines in Toronto office now reachable from SCL3, ateam wifi network set up. Just need a password for this and then we can move ahead.
Round Table
- [SETA] should it come to android?
- Now that desktop unittests are going live with SETA, we are looking into the future and see that 233/281 android jobs are not needed to catch all regressions on inbound/fx-team in the last 6 months.
- this would take some work from releng- but before we investigate we should see if it would be beneficial
- reducing tp4m and tsvgx pagesets- a lot of duplicated pages (in results and patterns), we could cut the list in half to reduce time and still catch all changes in the last year. In addition this sets us up for a softer landing on getting the tests running on autophone due to the reduced runtime.