Previous Action Items

Status reports

Dev team

Rel Eng

• nothing to report

A Team

• android-2-3-armv7-api9 Total failure rate: [1.14%]
  • last week 2.05%
  • total failure excluding retries 1.08%
• android-4-3-armv7-api11 Total failure rate: [1.99%]
  • last week 1.24%
  • total failure excluding retries 1.27%

Data fetched for: 2016-01-19 10:59 — 2016-01-25 22:00

• bug 1233220 Add an awsy-like test that tracks Firefox for Android memory use in perfherder
• Last of the Android 4.0 Debug reftests have been retired: only Talos running on Pandas now

Autophone

• bug 1238450 - Autophone - deploy Nexus 6P phones
  • Made pushed directories world writable
  • Used ifconfig with fallback to netcfg for getting ip addresses
  • Rooting remainder of Nexus 6Ps and running local tests before shipping to Mountain View.
  • Alleviated performance issues caused by need to chmod pushed directories by fixing bug 1242070 Autophone - adb.py - use native recursion with chmod when supported by the device. This improved job completion times significantly for devices which natively support chmod -R.
• Crashes due to external network accesses caused problems after new server deployment
  • bug 1239989 Autophone - PROCESS-CRASH | autophone-s1s2 | application crashed [@ nsSocketTransport::InitiateSocket]
    • Attempting to resolve external network accesses I fixed some issues in the served files and resolved a long standing issue in how the files are deployed on the web server. This helped but did not resolve the real issue which was bug 1241584.
  • bug 1241584 Autophone - moar external network accesses
    • Problem was a misconfigured phonedash url on autophone-3.
    • bug 1242011 Autophone - include host name in alert emails and Treeherder job details.
      • Adding host name would have helped diagnosing the issue more quickly.
• bug 1242846 autophone-1.qa.mtv2.mozilla.com down 2016-01-25
  • Server failed to reboot Monday evening. With help from Ashish, it was determined that the usb card failed and for some reason caused the machine to fail to boot completely.
  • We worked to move the devices which were connected to the card on autophone-3 by attaching them to the belkin hub and attaching that to autophone-3.
  • Root cause may be related to the USB A-USB C cable I purchased at Frys. nexus-6p-1 was connected directly to the card via this 3rd party cable while nexus-6p-2 was connected via the Belkin router. nexus-6p-1 suffered frequent disconnects which caused the server to reboot to recover. I had planned on asking someone to change nexus-6p-1 to use it's factory USB A - USB C cable and connect to the hub in the same fashion as nexus-6p-2 but the failure happened before I got around to it.
  • Plan going forward is to purchase 2 additional replacement USB cards of the same make and model. One to replace the card in autophone-1 and the other to act as a spare. In the future, I will do a better job of sourcing cables. If an additional card fails we will be able to swap the spare in while we determine a different/better card to use in the future.
  • We need to get a better handle on handling hardware issues especially with regard to how and when to call in HPE support.
• Updating test manifests to improve our test coverage.
  • Now that we have more devices available for testing and that job times have been reduced due to the chmod -R improvement it is a good time to think about which tests are run on which devices.
  • Mochitest DOM Media (Mdm) tests need more improvement before they can be run regularly. Currently they fail due to a variety of causes. Due to the way the mobile tests time out, these tests can take over 90 minutes. Such long running tests cause the servers to delay restarts for usb disconnection recovery for an unacceptable time. See Mdm mozilla-central. I have currently disabled Mdm on everything except Android 2.3 until run times are improved. They are still available via try however.
  • I have filed bug 1243408 - Autophone - update test manifests to better utilize new devices and improve test coverage. If you are interested in participating please let us know your preferences for test coverage.
• TODO - Planning for kbrosnan's Mountain View visit in February.
  • kbrosnan's visit to Mountain View in February will be a perfect opportunity to set up the additional Nexus 6Ps and install additional cooling pads. kbrosnan, bc and van should coordinate the activities.

Perfherder

Round Table

Action Items