EngineeringProductivity/Meetings/2011-12-19: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 4: Line 4:


=== Bughunter ===
=== Bughunter ===
* UI: A number of bug fixes and a few new features.


=== Eideticker ===
=== Eideticker ===

Revision as of 16:47, 16 December 2011

The Overview

Bugzilla

Bughunter

  • UI: A number of bug fixes and a few new features.

Eideticker

  • Green/red screen detection, to detect start/end of tests, nearly finished.
  • Increased efficiency in frame-processing code.

Marionette

  • Some work on getting gonk (new backend to replace "raw" android) working with qemu (Android emulator). Slow going, so work passed off to b2g team.
  • Made some improvements to pure JS tests; should land soon.

Mobile Automation

  • Started landing patches for reftest in native fennec; should be ready next week.
  • Almost ready to turn on talos tests for android-xul.
  • Mobile startup automation was turned back on with data running through on 2011/12/15 but froze a while later; ctalbert is debugging it.

Mozbase

Peptest

  • ahal working with aki to get peptest on try
  • added support for QA automation's shared modules

Robocop

  • Patches getting r+ed and legal review proceeding.
  • Patches will start landing 2011/12/16; working with releng on staging next week.

Tegra Pool

Talos

Speedtests

  • Nada.

Mozmill

  • Discussion proceeding on continuous integration of mozbase.
  • Getting ready to start rolling mozprocess/mozrunner into talos proper.

WebRTC

War On Orange

  • A few more small bug fixes.
  • Submitted a presentation abstract to TestIstanbul conference.
  • Going to start splitting long queries into many shorter ones to avoid excess load on ES server.
    • This will make it possible to add the tool to estimate when oranges were introduced ("Orange Seed") without killing the database. May renew interest in the War on Orange.

Upcoming Events

All times Pacific Time, click on link to find your timezone

Round Table

  • Rebooted brasstacks to see if that would magically fix the awful latency when accessing the ES database. It didn't, and a number of things failed to restart gracefully; mcote wrote up a summary (Intranet link) of what went wrong.
    • In the end, IT fixed the routing problem themselves. Access had only been granted to one of the three addresses that the ES server's hostname resolved to, resulting in a connection timeout 2/3 of the time.

Misc