Mobile/Testing/09 14 16

From MozillaWiki
Jump to: navigation, search

Previous Action Items

Status reports

Dev team

Rel Eng

A Team

  • (buildbot) android-4-3-armv7-api15 Total failure rate: [3.56%]
    • last week 4.01%
    • total failure excluding retries 2.11%
  • (taskcluster) android-4-3-armv7-api15 Total failure rate: [2.72%]
    • last week 3.17%
    • total failure excluding retries 2.18%

Data fetched for: 2016-09-05 20:30 — 2016-09-12 23:52

  • mochitest-gl hidden for jemalloc crashes
  • lots of intermittent startup crashes
    • some are Zip related -- esawin may have a fix

Autophone

  • [bc] Bug 1300890 - Autophone - Perf tests do not emit Treeherder recognizable failure log lines
    • Have been attempting to get this working in production. This works fine on my local Fedora 23 workstation, but in production on Ubuntu 16 fails to emit the test status messages to the log for the first initialized test instance but does emit them for the last. This means that s1s2 local test logs do not contain the TEST-PASS, TEST-UNEXPECTED-FAIL log messages which make it difficult for sheriffs to triage s1s2 failures for local tests. The test status messages do appear for the s1s2 remote test logs however. This was not a problem before we began relying on Treeherder to parse the logs since we handled the failures "manually".
    • Have been running development branches in production to test possible fixes.
  • [bc] Met with Armen regarding how to implement backfilling for Autophone. Seems reasonably straight forward to implement.

Perfherder

  • No recent apk size regressions

Round Table

Action Items