Previous Action Items

• dminor and mossop to talk

Status reports

Dev team

Rel Eng

• (Callek) landed bug 898227 Mozharness should release mozpool requests when it gives up waiting for the device to be ready
• (kmoir) landed bug 866875 Disable b2g-panda builds and GaiaUI-on-panda tests. Testing patches to run xpcshell tests on Android 4.0 on try bug 881293.
• hwine is working with IT/sheriffs to reschedule mozpool db move to an earlier date than Aug 24 to reduce number of retries bug 899379

IT

• PO for X86 infrastructure has been submitted to the vendor, waiting for delivery estimates.

A Team

Failure Rates

• tegra failure rate: [1.00%]
• panda failure rate: [26.09%]
  • excluding retries, failure rate is 2.19%

Mobile Bugs in Orange Factor Top 10

• bug 690176 Intermittent Android "talosError: 'initialization timed out'"
• bug 851861 Intermittent testOverscroll, testPanCorrectness, testAxisLocking, testLoad, testFlingCorrectness | Pixel at 100, 0 - Color rgba(0,0,0,255) not close enough to expected rgb(32,100,0)
• bug 807230 Intermittent DMError: Automation Error: Timeout in command {ls,ps,isdir,mkdr}, TEST-UNEXPECTED-FAIL | Automation Error: Timeout in command isdir /mnt/sdcard/tests/logs | Exception caught while running tests

Work in Progress

• Landed patch on bug 893085 as part of running remote cpp unittests from test package.
• Patch to fix panda reftest manifests at bug 900542
• Asked by js team to look at making jit-tests runnable on mobile bug 858622 which will require making a remote test harness and packaging the tests.

x86 automation

Autophone

• Mochitest-Canvas tests have been failing due to ImportError: cannot import name DEFAULT_PORTS. bug 870876 introduced a change which caused the error. Autophone has been updated to use the latest mozbase which resolved the issue. All phones except Nexus S and LG Revolution pass. Nexus S and LG Revolution stop running Mochitest after /tests/content/canvas/test/test_bug866575.html.
• S1S2 tests are running normally.

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

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