Previous Action Items

Status reports

android-4-3-armv7-api15 Total failure rate: [2.78%]
- last week 1.76%
- total failure excluding retries 1.92%

Data fetched for: 2016-03-22 03:31 — 2016-03-28 20:04

Geoff landed bug 1147918 Run autophone tests locally using mach
Completed Nexus 6P rollout with additional test manifest changes to improve Unit test coverage. bug 1238450 Autophone - deploy Nexus 6P phones.
Now running mochitest-dom-browser-element (Mdb), mochitest-media (Mm), mochitest-skia (Msk), mochitest-toolkit-widgets (Mtw), reftest-ogg-video (Rov), reftest-webm-video (Rwv).
- Mdm failures - esawin is looking into the timeouts in last test in bug 1232312 Autophone - Mdm failure - dom/media/test/test_webvtt_disabled.html
- Mm failures - looks like same issue as bug 1153860 - Autophone - PROCESS-CRASH | dom/media/test/test_played.html | application crashed [@ libc.so + 0x17ee4]
- Msk failures - Are these failures worth fixing? Do we care about running this test?
Additional load *may* have contributed to recent network issues with bug 1260426 Autophone - nexus-s-3 network disconnection and bug 1260217 Autophone - nexus-6p-6 disconnected

Chatted with gbrown and margaret about getting irc notifications for installer size changes (margaret's going to look at getting fennecbot to hook into perfherder's api for this)
Focus for Q2 will be (1) AreWeFastYet and (2) General bugfixing and feature improvements. Any requests?

[dminor] I didn't realize last week when I asked for media tests, it would run dom/media/test only. The tests I'm interested in are under dom/media/tests :)
- If it makes sense, I'd like to add a new autophone job to run those tests (WebRTC)
- try only to start with
- maybe only a subset of the tests to start with as well
- discussed this offline with bc, I'll try using autophone-mochitest-media and the autophone-media.ini for now

gbrown will try to find out about breadpad issues / no crash reports, especially for media