Confirmed users
3,990
edits
Mobile/Testing/07 11 12: Difference between revisions
→Action Items
| (9 intermediate revisions by 5 users not shown) | |||
| Line 9: | Line 9: | ||
= Status reports = | = Status reports = | ||
== Dev team == | == Dev team == | ||
* Investigated various test hangs: | |||
** Bug 759792 Robocop: "key dispatching timed out sending to" awesomebar | |||
** Bug 771189 Intermittent deadlock during CreateCompositor / surfaceDestroyed | |||
** Bug 769524 Frequent robocop testSearchSuggestions | GeckoEventExpecter - blockForEvent timeout: SearchEngines:Data | |||
** Bug 772672 CreateCompositor can hold up the Gecko thread, waiting for a surface | |||
** Bug 771862 Intermittent "command timed out: 2400 seconds without output" during Robocop tests, before launch | |||
* Next up: crashes / out of memory: | |||
** Bug 747787 Intermittent Tegra crash in libdvm.so during tests | |||
** Bug 757468 OutOfMemory exception on createBitmap after 330+ page loads | |||
== Rel Eng == | == Rel Eng == | ||
| Line 32: | Line 41: | ||
** many times I do the intial connection to copy the profile over and the sutagent is dead before I even try to launch the browser. I can remedy via adb reboot most of the time | ** many times I do the intial connection to copy the profile over and the sutagent is dead before I even try to launch the browser. I can remedy via adb reboot most of the time | ||
== S1/S2 Automation == | == blassey's ark (formerly S1/S2 Automation) == | ||
* Infrastructure and documentation work on AutoPhone (underlying framework). | |||
** There is a fair bit of design debt to be paid back, as this was a pretty ad hoc project that was repurposed several times. | |||
* bc is investigating run mochitests on phones. | |||
== Eideticker (not idle ticker) == | == Eideticker (not idle ticker) == | ||
* Can now zoom in on regions of dashboard for easier comparisons | |||
* Turned off XUL and stock android comparisons for LG G2X 2.2 on eideticker dashboard for now to save time generating results | |||
** QUESTION: Is there a benefit to continuing to get these? IMO (wlach) we have enough data on how we behave with these older browsers now. | |||
* Now using a new method to synthesize events on Android called Orangutan, this will affect dashboard results: http://wrla.ch/blog/2012/07/the-evolution-of-simulating-events-in-eideticker-from-monkeys-to-orangutns/ | |||
** QUESTION: Should we archive the old/historical results now? | |||
* Current version of devicemanager + agent not quite eideticker compatible. Patches to fix that in flight, already applied on the dashboard server. | |||
* Galaxy Nexus dashboard more-or-less ready to go, pending {{bug|759877}} | |||
* Working on making dashboard somewhat more resilient to failure: {{bug|771375}} | |||
* Hoping to start work on startup tests soon (blog posts on work-to-date forthcoming) | |||
* In Toronto next week to setup Eideticker machines there and give presentation to interested parties | |||
= Round Table = | = Round Table = | ||
* ready to order 50 panda boards? | |||
= Action Items = | = Action Items = | ||
* {{bug|772928}} <strike>Armen to file a bug to turn on reftests for ARMv6</strike> | |||
* Armen to get current lead time from digikey | |||
* {{bug|772959}} <strike>Armen to file bug tracking foopy-less setup work</strike> | |||