Mobile/Testing/05 23 12: Difference between revisions
Jump to navigation
Jump to search
(→A Team) |
|||
| Line 15: | Line 15: | ||
== A Team == | == A Team == | ||
* <12% [[https://docs.google.com/spreadsheet/ccc?key=0ArS97F99-BEZdEZDNUt2VmJlYWkxWTlJNlZYV2pMekE total failure]] rate - Thanks to Callek! | |||
* robocop still sucks, we need to do some work there to make it more reliable | |||
* reftests with browser.tabs.remote=false: reftest-sanity tests are causing a bunch of random oranges in reftest-1. Seems to be that CSSViewport stuff is complicating things. | |||
== S1/S2 Automation == | == S1/S2 Automation == | ||
== Eideticker == | == Eideticker == | ||
Revision as of 17:20, 23 May 2012
Previous Action Items
- ctalbert to file bug for nagios to monitor autophone and eideticker machines
- ted to ensure armv6 and x86 mozconfigs are checked into m-c for builds
- armenzg to schedule releng time for getting x86/armv6 builders going
- We're out of resources. TBH I don't know the way forward.
- Callek and Jmaher to investigate hanging bcontroller.py processes on trobo test - bug 752222, work to cleanup bcontroller.py zombie processes.
- ajuma/jmaher - get the 67 failures commented on in the manifest so we can turn on reftests with browser.tabs.remote=false
Status reports
Dev team
- Bug 756704 Robocop: missing / missed events can cause infinite hangs
- Bug 756817 Fix and reenable tcheck3 (and tcheck2?)
Rel Eng
A Team
- <12% [total failure] rate - Thanks to Callek!
- robocop still sucks, we need to do some work there to make it more reliable
- reftests with browser.tabs.remote=false: reftest-sanity tests are causing a bunch of random oranges in reftest-1. Seems to be that CSSViewport stuff is complicating things.