Mobile/Testing/12 04 13: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 14: Line 14:
== IT ==
== IT ==
== A Team ==
== A Team ==
* tegra failure rate: [[http://54.215.155.53/android_failures.html?platform=android2.2 1.22%]]
* panda failure rate: [[http://54.215.155.53/android_failures.html?platform=android4.0 13.6%]]
** excluding retries: 2.03
* Working on {{Bug|937637}} to get cpp unittests scheduled on trunk trees
* Can't attend this week due to a conflict
== x86 automation ==
== x86 automation ==
* All tests running hidden on Cedar, with some failures
* All tests running hidden on Cedar, with some failures

Revision as of 16:46, 4 December 2013

Previous Action Items

Status reports

Dev team

Rel Eng

IT

A Team

  • tegra failure rate: [1.22%]
  • panda failure rate: [13.6%]
    • excluding retries: 2.03
  • Working on bug 937637 to get cpp unittests scheduled on trunk trees
  • Can't attend this week due to a conflict

x86 automation

  • All tests running hidden on Cedar, with some failures
  • Complete:
    • kvm enabled and deployed: bug 929048
    • chunks coalesced, sets coalesced: bug 935214
    • patched emulator deployed: bug 933918
    • S1 split into 2 sets and output no longer duplicated: bug 939823
    • new AVD definitions (Graydon's) deployed: bug 919812
  • Working on:
    • cleaning up remaining failures: bug 936226

Autophone

Eideticker

Round Table

We have awful wait times on Tegras

  • We currently test Android 2.2 on Tegras
    • However, only less than 2% of our users are using Android 2.2
    • graydon is helping us to have an Android 2.3 story (10.82%-14.22% of our users)
  • We currently test Armv6 builds (~2% of users) and no-ion (we don't ship this - only b2g18 branches)
    • I want to know if we can have a not-per-checkin model testing for Armv6
    • This would improve our current 2.2 testing on Tegras

I think we're OK with Pandas wrt to capacity, however, I want to point out that 4.1 has passed 4.0 in number of users.

Action Items