Mobile/Testing/03 07 12
From MozillaWiki
Contents
Previous Action Items
- Joel to take care of Ts-moz-afterpaint
- finkle to give joel a list of perf tests he wants to write
-
ctalbert to grab 4 panda ES boards -
joduinn to order SD cards - Jmaher to drop panda for a bit and focus on robocop/talos
- Jmaher to follow up with mfinkle re perf tests post-mwc
- ctalbert to flash new ES board with build and see what new problems we find and what ends up fixed
Status reports
Dev team
No news this week.
Rel Eng
- bug 723667 - talos robocop
- jmaher landed OOM fix
- armenzg testing new build
- armenzg doing last test to make sure talos.zip changes work
- patches being reviewed
- jmaher landed OOM fix
A Team
Robocop:
- fixed OOM issue on pixel based tests
- runtime of ~35 minutes, we need to figure out how to speed this up as we get more tests
Reftests:
- bug 732498 - remove browser.tabs.remote=true from native fennec.
- 16 bugs filed to track reftest issues when we remove the pref, we need the dev team to start fixing these bugs before we can green up R2/R3.
Upcoming work:
- xpcshell in automation
- [power usage] tests
S1/S2 Automation
- Raw Fennec Startup
- ctalbert will work on uploading this to an external server
- we think we have the droid pro issue fixed
- phones are working with pulse and running tests daily now
Eideticker
- No news - same as last week. We can turn on this automation at any time.
Panda Boards
- [P1] bug 731669 (ctalbert) we can't reboot a panda board without using a PDU to reboot it
- hopefully the ES boards make things better
- [P1] bug 731670 (ctalbert) MAC address gets re-created on every reboot
- bug 731694 - SD cards have arrived
Carry over info
concerns
- IT is concerned about not having remote re-imaging
- the boards sometimes become unstable (much more than the tegras)
- each a-team member has a different experience on how to make things work
- hopefully the ES boards make things better
- armenzg: do we have an alternative to the panda boards?
- blassey: no fallback plan
- bug 725544 - Android 4.0 tracking bug
- Pandaboard Setup docs
Crash Stats
- Screenshot and data from 3/05/2012 2:28 PM PDT
Top crashes:
- see Stability Report 2012-03-06
- all Java crashes reported as of 3/05/2012 2:28 PM PDT
Note :
- Socorro/Breakpad work:
- bug 726385 Please create skiplist implementation for the Java field
- bug 726693 Some java crashes are not being mapped correctly to bugs in bugzilla even though the crash signature fields have the "signatures" listed
- bug 672606 - Aggregate numbers and topcrashes for Nightly and Aurora channels based on build ID date instead of crash date
- bug 727234 - Crash Report [@ EMPTY: no crashing thread identified; corrupt dump ]
- bug 727286 - Incorrect messaging when failing to submit a crash report
Should be fixed in next release:
Round Table
- Panda work priority
- I have stats saying that 3.0.x and 4.0.x together make a low market share
- I need more data to know what 4.0.x will be trending
- I will provide data later on
- We have to improve our purple/red VS orange/green ratio
- These bugs have been filed for long and are at the top of WOO
- bug 724738 - Intermittent Android mochitest and mochitest-robocop timeout
- bug 686084 - Intermittent Tegra "Cleanup Device failed" from "command timed out: 1200 seconds without output, process killed by signal 9"
- bug 687116 - Intermittent "unrecognized output format" running Talos on Android
- bug 722166 - Android tests intermittently just don't start
- Android 2.0.x distribution growth
2.0.x Jan. 23th, 2010 | 21% |
Apr. (3 months) | 30% |
Jul. (6 months) | 58.8% |
Mar. (14 months) | 93.9% |
- Android current distribution (as of Mar. 5th, 2012)
2.0.x | 93.9% (2.2 -> 25.3%, 2.3.x -> 62%) |
3.0.x | 3.3% |
4.0.x | 1.6% |
- Fennec 3/4.0.x distribution (data from February)
For release, we have 11.6% of our users on 3.0.x and 2.5% on 4.0.x. | For beta, we have 13.6% on 3.0.x and 4.9% on 4.0.x. |