Mobile/Testing/07 29 15

From MozillaWiki
Jump to: navigation, search

Previous Action Items

Status reports

Dev team

Rel Eng

A Team

  • android-2-3-armv7-api9 Total failure rate: [0.5%]
    • last week 0.52%
    • total failure excluding retries 0.41%
  • android-4-3-armv7-api11 Total failure rate: [1.39%]
    • last week 1.01%
    • total failure excluding retries 0.83%

Data fetched for: 2015-07-22 11:57 — 2015-07-28 18:51

  • After 2 years of doing this, dminor is retiring from failures rates effective this week. I'm not sure I remember the last time I attended this meeting :)
  • To get these numbers just visit: http://ouija.allizom.org/wiki_update.html and copy the contents into the wiki page.

Autophone

  • Some issues with reporting results to Treeherder. Need to improve error handling in Autophone.
  • Small regression in Throbber stop (at least) on June 16-17. Difficult to determine changeset but am investigating.
  • Investigating bug 1188935 - Autophone - Intermittent Java.lang.NullPointerException at android.net.nsd.NsdManager$ServiceHandler.handleMessage(NsdManager.java:350)
  • jmaher making good progress on Talos bug 1170685
    • code for tsvg and tp4m should be ready for second review tomorrow
    • slight refactor of autophone will be needed after landing tsvg/tp4m code
    • tcheck will start review process after refactor
    • then a need to resolve reporting numbers
    • finally determine scheduling: what devices, what branches, what configurations?
      • right now we only run on android 4.0 in a remote configuration, on all branches
      • I propose remote only tests on m-c builds, confirmation?
      • devices I don't know about- lets pick one 4.x device for now- thoughts?

Eideticker

  • python packaging/dep issues preventing it from working. trying to fix.

Round Table

Action Items