Confirmed users
3,376
edits
Auto-tools/Projects/Stockwell: Difference between revisions
Jump to navigation
Jump to search
new project definition
(create initial page) |
(new project definition) |
||
| Line 1: | Line 1: | ||
== | = Overview = | ||
* Stockwell comes from A*Team characters: https://en.wikipedia.org/wiki/List_of_The_A-Team_characters | |||
Mozilla has a problem with intermittent failures which are commonly known as "Oranges". These occur at an ever increasing rate and over the years many tools have been build and worked on to make managing the volume of these intermittent failures easier. Stockwell will provide a series of changes to the engineering workflow at Mozilla to have a longer term sustainable solution to these failures. Effectively we will turn intermittent failures into actionable items where all developers feel empowered and responsible for making things better. | |||
= Team = | |||
* | * [https://mozillians.org/en-US/u/geoffbrown/ gbrown] - triage, reproducability | ||
* [https://mozillians.org/en-US/u/jmaher/ jmaher] - policy, experimentation | |||
* [https://mozillians.org/en-US/u/wlach/ wlach] - developer hacking, tools | |||
= Meetings = | |||
Meetings are fortnightly on Friday 9am PDT | |||
Information and notes are on the [[https://wiki.mozilla.org/Auto-tools/Projects/Stockwell/Meetings meeting wiki]] | |||
= Problem = | |||
= Goal of the project = | |||
Reduce our intermittent failures when you push to <5 per push. | |||
* | |||
We will build tools, processes, and relationships to change the way we view testing and automation. When failures occur, we need to understand how realistic it is to fix the issue and give tools to developers to fix them if possible. If it is not realistic to fix the issue, we need to reduce the visibility and keep track of it in case it becomes severe and needs more serious time invested in it. | |||
= Non Goals = | |||
We will not be fixing every intermittent, nor will we be disabling all tests. | |||
= Dependencies / Who will use this = | |||
* sheriffs - they typically identify new intermittents | |||
* autostar - will be automatically categorizing intermittents | |||
* developers - will be fixing intermittents | |||
* testduty - new role (short term/long term) to triage and keep orange factor down | |||
= Design / Approach = | |||
* TBD in December | |||
= Milestones and Dates = | |||
* December 10th, 2016 - deliver plan to Mozilla Developers including plan for Q1, metrics to track | |||
* Q1, 2017 - implement plan, continue experiments | |||
* Q2, 2017 - repeat Q1, deliver report and 2017 Q3/Q4 plan in San Francisco to Mozilla developers | |||
= Implementation = | |||
* TBD in December | |||
= Getting Involved = | |||
We don't have a clear list of bugs, but when we do, they will show up here. If we determine we have mentored bugs, they will be easily discoverable here as well. | |||
<bugzilla> | |||
{ | |||
"quicksearch": "status:new,assigned,reopened,unconfirmed", | |||
"product": "Testing", | |||
"blocks": 1307197 | |||
} | |||
</bugzilla> | |||