Mobile/Testing/08 14 13: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "= Previous Action Items = * address roundtable item from this week in next weeks' meeting = Status reports = == Dev team == == Rel Eng == == IT == == A Team == * tegra failu...")
 
Line 17: Line 17:
* Work in progress on {{Bug|858622}} to run jit-tests on mobile
* Work in progress on {{Bug|858622}} to run jit-tests on mobile
* Landed patch for {{Bug|900542}} to fix up panda manifests
* Landed patch for {{Bug|900542}} to fix up panda manifests
** We are getting failures due to test suite running too long (need to break up into more chunks)
** We are getting many failures due to test suite running too long (need to break up into more chunks)
** Some new non-intermittent failures have shown up
** Some new non-intermittent failures, some are bugs, some need tweaks to range for fuzzy-if


== x86 automation ==
== x86 automation ==

Revision as of 14:40, 14 August 2013

Previous Action Items

  • address roundtable item from this week in next weeks' meeting

Status reports

Dev team

Rel Eng

IT

A Team

  • Mobile Bugs in Orange Factor Top 10
    • bug 690176 Intermittent Android "talosError: 'initialization timed out'"
    • bug 807230 Intermittent DMError: Automation Error: Timeout in command {ls,ps,isdir,mkdr}
  • Work in progress on bug 858622 to run jit-tests on mobile
  • Landed patch for bug 900542 to fix up panda manifests
    • We are getting many failures due to test suite running too long (need to break up into more chunks)
    • Some new non-intermittent failures, some are bugs, some need tweaks to range for fuzzy-if

x86 automation

Autophone

Eideticker

Round Table

  • It appears that the current version of sutagent (1.18) in the tree does not work reliably in production. Since our last aborted attempt to upgrade (see bug 885155), some code was added which should help diagnose the problems we thought we were having with finding the testroot (see bug 885365, but we have no evidence that the actual issue was fixed. What are the next steps here?

Action Items