Previous Action Items

• bug 772928 Armen to file a bug to turn on reftests for ARMv6
• 0 days - 500+ in stock - Armen to get current lead time from digikey
• bug 772959 Armen to file bug tracking foopy-less setup work

Status reports

Dev team

• Bug 757468 OutOfMemory exception on createBitmap after 330+ page loads
• Bug 774797 Robocop: upgrade to robotium-solo-3.3.jar
• Next up: Bug 747787 Intermittent Tegra crash in libdvm.so during tests

Rel Eng

Tegra

• Had a QTY-Of-Board-Useable problem on Monday unsure of the root cause at this time. We were down to 63 tegras connected to buildbot, out of the normal 130-150 connected at any given time, (out of our ~200 available boards) (bug 774986)
• ARMv6 Build Reftests planned to be deployed on Tegras, hoping to begin this work first thing next week. With the assumption that we are turning off some XUL suites (now, or very soon), to make the load not unbearable.

Panda

• bug 725544 - (android_4.0_testing) [tracking bug] Android 4.0 testing
  • bug 773517 - releng to test PDU setup - to be done this week
  • bug 769428 - provide usable image that can work (a-team)
  • bug 725845 - run 10 panda boards through buildbot staging systems

Beagle

• bug 767499 - (track-armv6-testing) Beagle Board Arm v6 Support Tracking
  • blocked on working image (a-team)

Other

• x86 onhold for now bug 750366
• Linux Foopy --
  • Created a new tegra-host-utils for Linux, based on a very recent m-c. (c.f. bug 742597 c#32 )
  • Working out load-requirements with RelOps (Looking like disk i/o is our largest concern, which happens in spikes rather than continuous. Evaluating hardware vs VMs)
  • In staging these are currently able to connect to buildbot, take a job, but we are failing to run xpcshell for unit-tests, and Talos tests are also failing to properly run.
  • Will be working more on this today/this-week to try and work out remaining issues.

IT

• Developing a remote re-imaging process for pandas bug 764534
• Working on a higher density chassis
• IT will be expanding in SCL1 Datacenter for mobile device housing
• 81 new tegras will be put into production pool bug 767447

A Team

• 36% failure rate. This is still bad with M3, M8, RC, R2, R3, TS, RPR being the biggest offenders.
• need to resolve tegras rebooting mid way through the test (this happens on all tests and xul and android, signs point towards infrastructure, but no proof) -- bug 772531

AutoPhone / S1/S2 Automation

• Project plan in place coordinating with releng: should be able to use some of this for foopyless tegras.
• Tests & refactoring continues.

Eideticker

• imgur test added
• Still working on a framework for getting backdated results into dashboard (bug 772948)
• Setting up Eideticker machines, phones in Toronto for use by developers (and for getting Eideticker working with B2G)
• Added rudimentary nagios monitoring for Eideticker setup in Mountain View (interim solution until server ops takes this over)

Round Table

• (armenzg) releng is constrained with people resources. I would like to have a list of priorities that we carry over on the meeting notes
• (kats) try server has lots of issues and is really slowing dev workflow (bug 770811, bug 772458).
• (armenzg) armenzg will be gone 3 weeks in August; Callek has stepped up to keep status of meeting

Action Items

• Jake to get an estimate for new tegras to be online - Response: https://bugzilla.mozilla.org/show_bug.cgi?id=767658#c4
• jmaher to figure out if turning off tests on m-c improved failure rate
• armen to send blassey a list of things on releng's plate
  • blassey to put that list in priority order (may take more than a week)
• ateam and releng to figure out the reboots