Mobile/Testing/09 26 12
Jump to navigation
Jump to search
Previous Action Items
- clint to look into bug 785032
Status reports
Dev team
- trying to reduce rc intermittent failures ... mixed success!
- want to have another look at bug 792212 on the tegras we have found that reftests fail a lot...
Rel Eng
Tegra
- Some tegras are being relocated in MTV this Friday
- no downtime is needed
- bug 793091 Treat all verify.py failures as cause for RETRY - deployed.
- Some minor messaging tweaks to sut_tools code, for sheriff sanity reviewed.
- Working on abstracting sut_tools code to remove "tegra" hardcodes.
- Adding back Android NoIon Builds (bug 793994)
Panda
Foopy-less
Other
- x86 onhold for now bug 750366
IT
- Developing a remote re-imaging process for pandas bug 764534 - in progress
- Working on a higher density chassis bug 777393 - moving forward with current H/W reqs to start designs
- IT will be expanding in SCL1 Datacenter for mobile device housing bug 774477 - in progress
- Setups 2nd chassis for smoketest bug 789516 - Pandas imaged, smoke tests running
A Team
- 8.18% total failure rate. m2, rc, and R4 are the biggest causes of failures.
- Panda board smoketests- still problematic, now we are not getting double agents, the board is not accessible (via SUT or ADB or even ping) after a reboot. Power cycles solve the problem each time.
- One option would be to only use the power cycle relay for reboots (via sut_tools instead of 'rebt' from sutagent)
- Looking into both patching fennec and changing the way reftests are run to resolve bug 792212. Seems like the problem is being triggered (probably just coincidentally) by the profile migration code and/or shared preference reading/writing. Thoughts on approach here?