malini, myself and others continue to work on supporting WebQA's automation of gaia smoke tests by fixing Marionette bugs and implementing enhancements

several people are working with rel-eng to try and get gaia smoke tests in running on pandas by Dec 10

have pref based work around for bug 800138, still need to follow up on what the right fix should be to start marionette after final-ui-startup but running with system context

Have fix for pandas do not boot with network enabled

Mozpool ready for roll out.

Last week:

Emulator tests on TBPL are again unhidden!

ahal is working on a bunch of minor issues to help make the tests more stable.

mdas and jgriffin are working to help stabilize Gaia smoke test automation. Currently, they are running (but buggy) in WebQA's Jenkins CI. Our goal is to get these into TBPL by Dec 10, either running on pandas or an emulator.

Regressions, regressions, regressions. Smoketest bugs are still hovering around ~16 a day, with some still not being commented or resolved within 24 hours. What can we do to continue driving priority on fixing these?

Logging discussion from earlier this week: default to no logs affects only Gaia logs? What about dogfooders?

Continuing to manually triage existing mochitests for addition into the manifest running on TBPL. Have found a significant number in /layout, a few elsewhere. Some fruit, slow going.

Working on automated method to walk the mochitests, execute file-by-file, and find passing candidates for inclusion. Spidering tests is easy, but framework hangs at the end of single test runs so execution is a little more complicated due to that.

dclarke driving effort to get permissions handling for functional API testing centralized into the mochitest harness. A-Team is providing harness knowledge, need more help from dev for B2G knowledge (fabrice?): https://bugzilla.mozilla.org/show_bug.cgi?id=814140