QA/Platform/Graphics/Triage

Get Involved

The triage sessions detailed below are typically done in private, simply because I'm doing it on my own at this point. If you'd like to get involved, either with me or on your own please, get in touch with me.

• E-mail: ahughes@mozilla.com
• IRC: ashughes in #gfx or #qa on irc.mozilla.org

See ashughes1.github.io for the session schedule and statistics.

Schedule

Category	Next Session
Help Wanted Bugs	Monday, May 9, 2016 at 10:00am Pacific
Incoming Bugs	Tuesday, May 10, 2016 at 10:00am Pacific
Top Crashes	Wednesday, May 11, 2016 at 10:00am Pacific
Cold Crashes	Thursday, May 12, 2016 at 10:00am Pacific
Cold Tracked Bugs	Friday, May 13, 2016 at 10:00am Pacific
Real-time schedule available on ashughes1.github.io

Stats

Date	Help Wanted	Incoming	Top Crashes	Cold Crashes	Cold Trackers
2016-04-15	25	194	12	387	15
2016-04-22	18	198	14	410	0
2016-04-29	4	179	15	407	0
2016-05-06	4	182	16	386	0
Change from last week	0	+3	+1	-21	0
Change since beginning	-21	-12	+4	-1	-15
Real-time data available on ashughes1.github.io

Help Wanted

Once per week, typically on Monday, we review bug reports tagged with help-wanted older than 30 days to ensure these issue are still relevant and on track to resolution.

How to Triage:

1. Select a bug from this list
2. Review the bug to make sure you understand the bug report and the information needed to move it forward
3. Attempt to reproduce the bug
4. If you can reproduce the bug, attempt to find a regression window either manually or using mozregression
5. Update the bug report with any new information you can provide
6. If you can't reproduce the issue or don't understand the issue, move on to the next bug report

Whenever updating a bug report be sure to add a comment explaining the change.

Incoming

Once per week, typically on Tuesday, we review bug reports that were reported more than 30 days ago but have yet to be triaged by the Graphics team.

How to Triage

1. Select a bug from this list (it's best sort by most recent changed first)
2. Review the information in the bug and make sure you understand the issue
3. If the bug is a feature request, add the feature keyword and move on to the next bug
4. Request for information from the report if there is information missing (regression window, steps to reproduce, minimized testcase, screenshots, system information, etc)
5. If you can reproduce the issue as described then update the bug and escalate it to a graphics developer
6. If you cannot reproduce the issue, ask a developer or the reporter if the bug is still valid
7. Be sure to add the gfx-noted tag to the whiteboard field once triaged
8. Move on to the next bug report if you can

Top Crashes

Once per week, typically on Wednesday, we review our top crash reports to ensure these issues have bug reports on track toward resolution.

• Explosiveness Report: http://bit.ly/1N9iR7j
• Firefox Topcrash Report: http://bit.ly/1VqmLMm
• Fennec Topcrash Report: http://bit.ly/1N9iTfG

How to Triage

Note: Whenever updating a bug report be sure to add a comment explaining the change.

1. Review the reports above
2. If you see a graphics crash that doesn't have a bug report, file a bug report for it
3. If you see a graphics crash with an associated bug ID, open the bug report and update the statistics for the bug
4. If the crash is escalating and is now in top-crash territory, add the topcrash keyword and nominate the bug to track
5. If the crash is declining and is no longer in top-crash territory, remove the topcrash keyword
6. Repeat the process for each crash you find in the list

Cold Crashes

Once per week, typically on Thursday, we review crash bug reports we have on file that have not been updated in more than 30 days to ensure these issues are still relevant and on track to resolution.

How to Triage:

1. Load this list of bugs and sort by most recent changed
2. Open the first bug report and review the information
3. Check if there are anymore crash reports by clicking the signature link
4. If there are no more crash reports, close the bug
5. If there are still bug reports, update the statistics in the bug report and see if you can reproduce
6. If you can't reproduce, ask the reporter for new information
7. If you can reproduce, ask the developer what information is needed to move the bug forward
8. Update the bug with any new information and move on to the next bug report

Cold Trackers

One per week, typically on Friday, we review tracked bug reports that have not been updated in more than 30 days to ensure these issues are still relevant and on track to resolution.

How to Triage:

1. Select a bug from this list (sort by most recent changed)
2. Review the information in the bug report
3. Try to deduce if the bug is still relevant through testing, reviewing linked reports, or asking people involved on the bug
4. If the bug is still relevant, update the status/tracking flags, and needinfo flag the developer for a status update
5. If the bug is no longer relevant, update the status flags and close the bug report
6. Once you've updated the bug move on to the next bug report