Mobile/Testing/12 11 13: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 19: Line 19:
== A Team ==
== A Team ==
* tegra failure rate: [[http://54.215.155.53/android_failures.html?platform=android2.2 3.25%]]
* tegra failure rate: [[http://54.215.155.53/android_failures.html?platform=android2.2 3.25%]]
** Possibly due to large backlog of tegra tests to run?
* panda failure rate: [[http://54.215.155.53/android_failures.html?platform=android4.0 20.21%]]
* panda failure rate: [[http://54.215.155.53/android_failures.html?platform=android4.0 20.21%]]
** excluding retries: 2.09
** excluding retries: 2.09

Revision as of 16:31, 11 December 2013

Previous Action Items

Status reports

Dev team

Rel Eng

  • Disabled tcanvasmark on pandas, everywhere
  • In bug 918168 Marked 44 tegras as decomissioned due to varying obvious signs of bad hardware (I can chat off-meeting with anyone who cares for more information on how I determined 'bad')
  • IT Recovered a whole bunch of pandas in bug 902657 at releng urging.
    • Most common issue was failing sdcard
  • IT Recovered a large swatch of tegras which fell through cracks by releng in bug 944498
  • coordination continues on planning 650-castro evac of tegra infrastructure to scl3. More info as it gets locked down.

IT

A Team

  • tegra failure rate: [3.25%]
    • Possibly due to large backlog of tegra tests to run?
  • panda failure rate: [20.21%]
    • excluding retries: 2.09
    • last week's failure rate was 13.6%, retries are the culprit
  • Cpp unittests now scheduled and riding the trains (thanks bhearsum!)
  • Landed fix for bug 945273 to get panda reftests green again

x86 automation

  • All tests running hidden on Cedar, with some failures
  • Working on:
    • cleaning up remaining failures: bug 936226
    • biggest remaining problem is intermittent loss of connectivity: bug 927602

Autophone

Eideticker

Round Table

Action Items