Quantum/Release Criteria: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Ignore bugs blocking QRC meta bugs that have assignees)
m (→‎Bug Workflow: bold state names)
Line 5: Line 5:


QRC bug states:
QRC bug states:
* "[QRC_NeedAnalysis]" and unassigned (ready for profile analysis)
# '''"[QRC_NeedAnalysis]"''' and '''unassigned''' (ready for profile analysis)
* "[QRC_NeedAnalysis]" and assigned to an engineer analyzing the profile
# '''"[QRC_NeedAnalysis]"''' and '''assigned''' to an engineer analyzing the profile
* "[QRC_Analyzed][qf]" and unassigned (ready for QF triage)
# '''"[QRC_Analyzed][qf]"''' and '''unassigned''' (ready for QF triage)
* "[QRC_Analyzed][qf:" and assigned to an engineer fixing the bug
# '''"[QRC_Analyzed][qf:"''' and '''assigned''' to an engineer fixing the bug


# Testers will:
# Testers will:

Revision as of 18:52, 29 May 2017

QRC = Quantum Release Criteria QF = Quantum Flow

Bug Workflow

QRC bug states:

  1. "[QRC_NeedAnalysis]" and unassigned (ready for profile analysis)
  2. "[QRC_NeedAnalysis]" and assigned to an engineer analyzing the profile
  3. "[QRC_Analyzed][qf]" and unassigned (ready for QF triage)
  4. "[QRC_Analyzed][qf:" and assigned to an engineer fixing the bug
  1. 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 Gecko Profiler profile.
    4. Add the whiteboard tag "[QRC_NeedAnalysis]".
  2. Engineers on the "Profiler Overflow" list:
    1. Select a bug from the "Bugs Ready To Be Analyzed" list below.
    2. If the bug has no profile is attached, then needinfo the reporter and select a new bug.
    3. Assign the bug to yourself while you are analyzing it.
    4. If you can't identify the root cause, then unassign yourself and select a new bug. Another engineer will pick it, so leave any useful notes or needinfo someone who may have domain knowledge relevant to the profile.
    5. Once you have identified the root cause, then:
      1. Change the whiteboard tag from "[QRC_NeedAnalysis]" to "[QRC_Analyzed][qf]" (so the bug will be seen by Quantum Flow triage).
      2. Move the bug to an appropriate Bugzilla component.
      3. Unassign yourself.

Bugs Ready To Be Analyzed

Full Query
ID Priority Summary Whiteboard Keywords Assigned to
1363352 -- Amazon homepage start: time to first nonblank is slow [QRC][QRC_NeedAnalysis]
1363354 -- [meta] YouTube first video play is slow [QRC][QRC_Analyzed] meta, perf
1365835 P5 Lots of time spent in createScriptForLazilyInterpretedFunction() when playing a youtube video [QRC][QRC_Analyzed] perf
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] perf
1367658 -- [Input Latency] Firefox is 600% (118 ms) slower than Chrome in case GSearch - Search Suggestion Selection [QRC]
1371646 P3 Amazon access book result navigation profile [QRC][QRC_Analyzed][platform-rel-Amazon] perf Jonathan Kew [:jfkthame]
1371659 P3 Google Search profile [QRC][QRC_Analyzed] perf
1371661 P3 Google image search profile [QRC][QRC_Analyzed] perf
1381384 P2 Performance analysis on gmail_ail_compose_new_mail_via_keyboard [QRC][QRC_Analyzed] perf
1381385 P3 gmail_ail_open_mail for QRC_NeedAnalysis [QRC][QRC_Analyzed] [gfx-noted] perf
1381387 P3 Performance analysis on gmail_ail_reply_mail [QRC][QRC_Analyzed] perf
1394761 P3 Hasal input latency case facebook_ail_scroll_home_1_txt regressed median from 22ms to 44ms on 7/29 [QRC][QRC_NeedAnalysis] perf

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


Bugs that block QRC meta bugs but have no QRC or QF whiteboard tags:

Full Query
ID Priority Summary Whiteboard Keywords Assigned to
1351769 P3 [meta] Meta: Quantum Flow JS Changes Meta-Bug meta, perf
1376323 P3 Speed up StripCRLF()
1377560 P2 Don't keep nsContentList's alive
1720061 P3 [Meta] Setting input.value when input has focus is 1.2x slower than Chrome on Android meta, perf

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


Bugs Now Being Analyzed

No results.

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


Bugs Ready To Be Assigned

This profile case is analyzed. A root cause was determined and a component was assigned.

No results.

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