Mobile/Testing/12 07 11
From MozillaWiki
Contents
Previous Action Items
Status reports
Dev team
Rel Eng
- deployed
- bug 704555 deploy rss for tp4m on android
- bug 693352 minidump/stackwalk
A Team
- we have 9.76% orange rate:
- previous weeks were: 4.13%, 3.01%, 2.43%
- [spreadsheet]
- most of this is due to merge of birch to m-c and network outages and infrastructure issues
- RSS for android is landed and live [graph]
- Minidump Stackwalk is landed and live
- bug 704509 - Android Reftests waiting for review
- bug 701076 - Robotium for Android; polishing up tests and docs, have geoffbrown involved now. We should be ready to start writing tests now and can work on reviews and landing over the next week.
S1/S2 Automation
- added queuing system to fix deadlocks and run jobs with a given changset
- network outages are causing database to be down, still need to verify we have fixed the results logging
- potential fix for the networking issue on the nexus phones
Round Table
-
What to do about xul browser-chrome and reftests - We need to resolve results posting from android/android-xul to graph-server. It appears they are both posting to the same graphs!
- other tools might have the same problem (as my spreadsheet for the failures does)
- noise in perf tests. What can we do about it?
- B2G - when do we need to start planning for it? (bear)
Action Items
- joel/geoff to write up "how to write a robotium test"
- finkle to investigate automated test writer
- joel/bear to figure out what to do about graph server
- naoki to look at:
- killing the market process
- using more runs to smooth out data
- throw out any run that has a dalvik GC in it