Mobile/Releng/10 12 12
Jump to navigation
Jump to search
- Whole picture: https://releng.etherpad.mozilla.org/mobile-workload
- Etherpad: https://releng.etherpad.mozilla.org/mobile-releng-notes
- Last mobile testing meeting: https://wiki.mozilla.org/Mobile/Testing/10_10_12
- Notes stored at: https://wiki.mozilla.org/Mobile/Releng/10_12_12
NOTE: These are the notes for Oct. 12th, 2012
Previous action items
(kmoir) to follow up with jmaher about if there are any tests that we can try for Android 4.0/panda and Fennec - From jmaher "I recommend the mochitests (1-8) as the first tests. If you are wanting to run the smoketests, I have a pending todo to write documentation up about that."(kmoir) file tracking bug for dry run and staging setup https://bugzilla.mozilla.org/show_bug.cgi?id=799698- (carry over) armenzg to add quick search suggestions for next week
- I want to remove it from the action items and I will get to it whenever I can rather than dragging it
(hwine) to file LifeGuard bug https://bugzil.la/798455- (armenzg) to follow up with ctalbert about LifeGuard
- jgriffins wrote the spec and mcote will be working on it. more info to come
Now
List here bugs that are currently being worked on or that it needs attention:
- (ctalbert) SD card issues with new Tegras
- https://bugzilla.mozilla.org/show_bug.cgi?id=785032
- ctalbert has a theory, Callek to stage SUTAgent and Watcher apks on a handful of tegras next week, including some new ones likely.
- The SUTAgent and watcher code has some debugging info to help figure out the issue, but likely will need more changes.
- [waiting on review by Callek] add a pdu cycle to the sut_tools for reboots instead of dm.reboot
- (Callek) Clientproxy is stopping tegra buildbot instances in some cases where it seems we shouldn't really be.
Done
This section will gather what we accomplished in the last week:
- (jmaher) update sut_tools to use modern devicemanager
- (jmaher) update sut_tools to use a more modern logging infrastructure
- (callek) coerce waitForDevice to retry a sane amount of times
Dry-run for ICS pandas
TRACKING BUG: https://bugzilla.mozilla.org/show_bug.cgi?id=799698
- (Callek) Move tegras.json to devices.json
- https://bugzilla.mozilla.org/show_bug.cgi?id=794743
- reviewed, will stage/land early next week.
- ? - order and configure suffient foopies/build masters to support new panda boards
- create a panda.json Add panda info to devices.json to map device names/ip -> relay:bank:slot
- setup 5 foopies for pandas
- [BLOCKED] on pandas imaged correctly <= SHOULD BE UNBLOCKED TODAY
- https://bugzilla.mozilla.org/show_bug.cgi?id=790339
- naming of boards: panda-XXXX seems likely
- Officially Decided as panda-XXXX
- nagios checks
- master (done), foopies (done), pandas (just double check)
- tbpl changes
- waiting for job names
- resolve sut_tools (including remote pdu cycling)
- This can be a non checked in version as long as we have patches on bugs
- bug 797868 tracking this work.
- add panda* to the graph server for when we run talos
- I need a list of final names that we will use, can I assume panda-000 -> panda-314, or will we want panda-0000 -> panda->0314 ?
- panda-0001 -> panda-0460 is a good shot at the starting names
- add support in buildbot to schedule panda and tegra jobs for android opt builds
- add support in buildbot for running panda test jobs
- build out 5 foopies (hardware is here, 1 is setup for smoketests)
B2G pandas
- (IT/A-team) Image 12 pandas for B2G by hand by 10/9/12
- (armenzg) Store Gecko builds
- (armenzg) Add WebAPI tests on emulator
Round table
List items that need discussion.
- (hwine) update on panda board progress
- (kmoir) given the number of possible devices coming online (400-800) eventually, should we be looking at a foopyless setup
- b2g testing process will involve re-imaging on every run