QA/Execution/Web Testing/roles/buildmaster

From MozillaWiki
Jump to: navigation, search


The buildmaster role is assigned to a team member in rotation, each lasting two weeks. The role is intended to identify failures early, and to take action towards resolving the failures. This action will vary depending on the skills and knowledge of the current buildmaster, or the level of commitment the team has to the affected project.

Monitoring Failures

Failures can be monitored in the following ways:



  • in Jenkins, on the failing job's output, you'll see "This build was not claimed. Claim it." Click on Claim it and add your relevant details.
  • you'll now be the Assignee, and you and your investigation details should now show up next to the failing build, on
  • if you know or suspect the failure's root cause does or will affect other jobs/projects, send an email to either the public (preferred) or internal mailing list, as appropriate
  • once/when the build passes, your claim and the failing job will automatically be removed from the Claims view


  • serves as a "backup" in case of vacation/PTO
  • both Owner and Co-owner should coordinate to help ensure continued coverage
  • prompt the Owner with an offer for help, when there doesn't appear to be traction/visibility


The Web QA Buildmaster Rotation page contains the past and upcoming schedule.

These entries are in reverse chronological order.

  • 2016-05-05 - 2016-05-19 - stephend
  • 2016-04-21 - 2016-05-05 - mbrandt
  • 2016-04-07 - 2016-04-21 - davehunt
  • 2016-03-24 - 2016-04-07 - rbillings
  • 2016-03-10 - 2016-03-24 - krupa

Known Issues

For the latest known issues check this etherpad. If you are the current buildmaster please try to keep this pad updated. It helps when it comes to hand the role onto the next buildmaster, and can avoid duplicating effort investigating failures.

New Failures

When a new failure is found, details should be added to this etherpad and an issue should be raised in the appropriate place (see projects section for details). This is the minimum expected of the buildmaster, however if you have the time and skills (or time to learn the skills), it's a good idea to try to replicate the failure locally. If the failure is clearly something that should be fixed in the test suite, then it's also appreciated if you can submit a pull request with a fix.


Add-ons (AMO)

  • Priority: High
  • IRC: #remora
  • Bugs: Open Bugs, Raise Bug
  • Contacts:
    1. Krupa Raj [:krupa]
    2. Mathieu Agopian [:magopian]
    3. Wil Clouser [:clouserw]


  • towards low priority
  • fail: john morrison [jrgm] if infrastructure related (time outs, buttons not loading, etc.); bob or davehunt are the ones to fix
  • IRC: #identity
  • known bug file bug and also need info him; esp if you know who checked in the change who made it fail


Hello (Loop)


mozwebqa dashboard

One and Done

Crash Stats (Socorro)


Support (SUMO)

  • Priority: Low
  • IRC: #sumodev
  • Bugs: Open Bugs, Raise Bug
  • Contacts:
    1. Rebecca Billings [:rbillings]
    2. Michael Cooper [:mythmon]
    3. Rehan Dalal [:rdalal]


Which bugs are currently open that correspond to known test failures?

The buildmaster maintains an etherpad which lists bugs that currently impact jobs.

Who do I contact if the issue is related to Persona?

If you trace an issue to Persona (the sign-on service) you should contact :jrgm in #persona. You can also raise issues in the project's GitHub repository.

Who do I contact if the issue is related to Firefox Accounts?

If you trace an issue to Firefox Accounts you should contact one of the following in #fxa: Shane Tomlinson (stomlinson), Zachary Carter (zaach), or Vladislav Filippov (vladikoff).

Why is the failure only happening on Sauce Labs?

It could be that the failure is only presenting itself on specific browser window sizes. Sauce Labs uses virtual machines with screen resolutions that may differ from our internal Selenium Grid. You could try specifying a browser window size to make the results consistent, or at least consider how the size of the browser might affect the tests that are failing.