Bug Workflow

A QRC bug is a bug that indicates Firefox is below some performance target on a QRC benchmark or metric.

QRC bug states:

"[QRC][QRC_NeedAnalysis]" and unassigned (ready for profile analysis)
"[QRC][QRC_NeedAnalysis]" and assigned to an engineer analyzing the profile
"[QRC][QRC_Analyzed][qf:p1]" and unassigned (ready to be fixed by a QF engineer)
"[QRC][QRC_Analyzed][qf:p1]" and assigned to a QF engineer fixing the bug

Testers will:
1. File a new bug for any QRC test failures that don't already have a bug.
2. Make the new bug block one of the QRC meta bugs.
3. Attach a link to a Gecko Profiler profile.
4. Add the whiteboard tag "[QRC][QRC_NeedAnalysis]".
Profile analysis engineers on the "Profiler Overflow" list:
1. Select a bug from the "Bugs Ready To Be Analyzed" list below.
2. Assign the bug to yourself while you are analyzing it.
3. If the bug is invalid or not actionable, then needinfo the reporter or close the bug.
  - There might not be obvious, visible problems. The profile analysis does not necessarily require the profile analysis engineer to reproduce the test case, just identify if there are obvious hot spots in the profile.
4. If you can't identify the root cause, then unassign yourself. Another profile analysis engineer will pick it from the QRC_NeedAnalysis list, so leave any notes you have or needinfo someone who may have domain knowledge relevant to the profile.
5. If you have identified the root cause, then:
  1. Change the whiteboard tag from "[QRC_NeedAnalysis]" to "[QRC_Analyzed][qf:p1]" (so the bug will be seen by QF engineers).
  2. Move the bug to an appropriate Bugzilla component.
  3. Unassign yourself.

Resources on "How to do Gecko Profiling"

If you have questions about using the Gecko Profiler, operators are ready standing by to help in the #flow IRC channel. :)

Ehsan's videos on how to analyze Gecko profiles

Mike's deep dive videos analyzing profiles on real bugs

QRC_NeedAnalysis bugs:

Full Query

ID	Priority	Summary	Whiteboard	Assigned to
1363352	--	Amazon homepage start: time to first nonblank is slow	[QRC][QRC_NeedAnalysis]
1394761	P3	Hasal input latency case facebook_ail_scroll_home_1_txt regressed median from 22ms to 44ms on 7/29	[QRC][QRC_NeedAnalysis]

2 Total; 2 Open (100%); 0 Resolved (0%); 0 Verified (0%);

QRC_NeedAnalysis bugs:

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

QRC_Analyzed bugs that are ready to be fixed by a QF engineer:

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

QRC_Analyzed bugs that are missing the [qf:p1] whiteboard tag:

Full Query

ID	Priority	Summary	Whiteboard	Assigned to
1363354	--	[meta] YouTube first video play is slow	[QRC][QRC_Analyzed]
1363403	P3	Facebook profile navigation start: access the user photo profile from a post	[QRC_Analyzed]
1365835	P5	Lots of time spent in createScriptForLazilyInterpretedFunction() when playing a youtube video	[QRC][QRC_Analyzed]
1367352	P3	[Input Latency] Firefox is 63% (35 ms) slower than Chrome in case Facebook - click right arrow on photo viewer	[QRC][QRC_Analyzed][gfx-noted]
1371646	P3	Amazon access book result navigation profile	[QRC][QRC_Analyzed][platform-rel-Amazon]	Jonathan Kew [:jfkthame]
1371659	P3	Google Search profile	[QRC][QRC_Analyzed]
1371661	P3	Google image search profile	[QRC][QRC_Analyzed]
1381384	P2	Performance analysis on gmail_ail_compose_new_mail_via_keyboard	[QRC][QRC_Analyzed]
1381385	P3	gmail_ail_open_mail for QRC_NeedAnalysis	[QRC][QRC_Analyzed] [gfx-noted]
1381387	P3	Performance analysis on gmail_ail_reply_mail	[QRC][QRC_Analyzed]

10 Total; 10 Open (100%); 0 Resolved (0%); 0 Verified (0%);

QRC queries: