Mobile/Testing/06 06 12
From MozillaWiki
Contents
Previous Action Items
Status reports
Dev team
Rel Eng
- Android armv6 builds created
- patches will be polished
- bug 750366 - Android x86 builds waiting on dependent bugs
- blocked on bug 756816 "x86 GCC is linked against a too-new glibc"
- bug 723667 - philor fixed talos robocop code for mozilla-beta
- The URL for getting the fennec_ids.txt was incorrect
- bug 761500 - 21600 seconds without output is a very long time to wait on Talos runs.
- Shortens up our timeout, since these tests sure don't need 6 hours to run anymore. New timeout is 1 hour.
- bug 753260 - cleanup is finally killing off (dead) bcontroller.py (from robocop) processes when run.
- This might help eliminate a lot of the hung robocop runs for 12+ hours or so we have seen. (Though those hangs could be unrelated to the dead processes entirely, hard to say for sure right now).
A Team
- [test status spreadsheet] - 22% total failure rate for all tests, appears that we are having robocop, reftest and the normal talos reds.
- bug 761125 - create android-failures.json of tests to not run instead of android.json which is a list of tests to run. This will take us from about 24000 tests to >270000 tests.
S1/S2 Automation
Eideticker
- Priorities, as always, being tracked here: https://etherpad.mozilla.org/eideticker-priorities
- Dashboard sadly still down, pending a fix to bug 759200 (Connection between WIFI network and physical network in hax0r is super slow)
- Did first benchmarks of native fennec perf. on Galaxy Nexus vs. the competition, information handed off to product managers
- Need to do some cleanup work from getting the GN to work, then probably onto integrating Eideticker with SPS profiling
- wlach on vacation from the 18th June - 2nd July, work on Eideticker likely on hold until he gets back (we have someone to cover keeping the dashboard up assuming the issues above are resolved)
Round Table
- We need to ensure that our Robocop documentation is still accurate and update it if not
- where are we on battery usage tests?
- can we make talos test to track cpu usage and event loop load in the background?
Action Items
- blassey to add IT status to template
- blassey to make sure bugs get on file for background talos tests