Previous Action Items

• clint to look into bug 785032
• wlach to update patch on bug 792212 and request review from gbrown and gcp

Status reports

Dev team

• Trying to find root cause for reftest-failures-on-new-tegras
•  :gbrown on PTO starting Friday

Rel Eng

Tegra

• [DONE] (IT) Tegras got moved without any trouble
  • https://bugzilla.mozilla.org/show_bug.cgi?id=793089
• [DONE] (Callek) Re-enable non-IM armv7 builds
  • https://bugzilla.mozilla.org/show_bug.cgi?id=793994
• [WIP] - (Callek) Move tegras.json to devices.json
  • this is preparation for panda boards
  • https://bugzilla.mozilla.org/show_bug.cgi?id=794743
• [DONE] (Callek) no-ion builds fail in make upload
  • https://bugzilla.mozilla.org/show_bug.cgi?id=795026
• kudos to jmaher for helping us out with moving into the present
• (jmaher) update sut_tools to use modern devicemanager
  • https://bugzilla.mozilla.org/show_bug.cgi?id=795028
• (jmaher) update sut_tools to use a more modern logging infrastructure
  • https://bugzilla.mozilla.org/show_bug.cgi?id=795071

Panda

Foopy-less

Other

• x86 onhold for now bug 750366

IT

• Developing a remote re-imaging process for pandas bug 764534 - in progress, integration testing next week
• Working on a higher density chassis bug 777393 - moving forward with current H/W reqs to start designs
• IT will be expanding in SCL1 Datacenter for mobile device housing bug 774477 - in progress
• Setups 2nd chassis for smoketest bug 789516 - Pandas imaged, smoke tests running
• Unable to connect to Panda_023 after power cycle bug 796000

Jake is out for PTO/Wedding from 10/18-11/2.

A Team

• [6.55% total failure rate] - trending in the right direction here
  • R3 and R4 are the problematic cases here

• panda smoketests
  • using pdu reboot for all cases successfully
    • note: it has been mentioned we should try software reboot first, then fall back to pdu (a future work item)
    • note: we will need to agree on a format for the pdu->device mapping and how we will store this and reference it
  • patches are in staging (on existing tegras) for core sut_tools changes
  • there are watcher and sutagent changes required
  • need to generate a new panda image as our initial master

Autophone

• Identified cause of failure in three phones: old SUT agent! They have been upgraded.
  • Investigation notes in bug 793961.
• Two phone (droid pro and sensation) still out of commission. They are refusing to reboot from the agent.
• 6 phones have been running smoothly for about a week. Only hiccup was changing IP addresses on two phones when DNS was fixed (bug 791417). Filed bug 797371, which, with bug 795195, should prevent this problem in the future.
• Started work on extracting device pool from Autophone.
• Dashboard improvements landed and deployed to http://mrcote.info/phonedash/. Much much faster, and a couple UI improvements.

Eideticker

• Did some custom runs to try and track down the cause of DLBI problems
• Some more work making it easier for developers to do custom runs on the machines in MV when they're idle
• Adding a pinch-zoom function to event simulation to help debug that use case (bug 797137)

Round Table

• (blassey) check point
  • time line for pandas? [end of next week 10/12]
    • (armenzg) what blockers do we have to order 400 panda boards for Android 4.x testing?
    • ctalbert, moconnor, blassey says GO for it
  • time line for ARMv6? [very fuzzy, end of quarter]
  • time line for Noah's arch?
    • Next step add more devices on S1/S2 (timeline TBD)
• (armenzg) testing matrix clarification
  • armv7 on tegras
  • armv6 on tegras (for armv6 test coverage)
  • armv7-non-IM on tegras (for b2g test coverage and armv6 indirectly because for old Jaegermonkey code test coverage)

Action Items

• Clint to put together an ARMv6 check list
• Blassey to get clint a list of desired devices for autophone

Panda Check List

• A-team to deliver image to IT (ETA 10/5)
• IT to image cards (ETA 10/10)
• RelEng to confirm that foopies are ready for pandas (ETA 10/10)