New test environments: Difference between revisions

Jump to navigation Jump to search
→‎Green up tests: expand section
(→‎Green up tests: wip to expand greening up section)
(→‎Green up tests: expand section)
Line 260: Line 260:


and so on.
and so on.
Mochitest is a particularly large suite and has many subsuites, so it may be good practice to create a meta bug for each mochitest subsuite.


A useful reference is the [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1572242&hide_resolved=1 Debian 10 meta] bug.
A useful reference is the [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1572242&hide_resolved=1 Debian 10 meta] bug.
Line 280: Line 282:
* in the new pane that pops above the Failure Summary, click on Save.
* in the new pane that pops above the Failure Summary, click on Save.


=== Example (with previously logged bug that does not match description) ===
=== Example (no bugs match description or no bugs filed for particular failure) ===


* follow the same steps as above, until the second to last step.
* follow the same steps as above, until the second to last step.
* since none of the bugs suit the description, click on the bug icon beside the error description.
* open an instance of the <code>live_backing.log</code> in a separate tab.
* since none of the bugs suit the description or no bugs have been filed for this particular failure, click on the bug icon beside the error description.
* a new overlay will show titled Intermittent Bug Filer.
* a new overlay will show titled Intermittent Bug Filer.
*  
* use <code>./mach bugzilla-component file-info <file_path></code> to identify the bug component.
* prefix the bug title with an appropriate name for the platform.
* in the body, specify the platform, subsuite and paste the relevant portion of the log.
* fill in the <code>blocks</code>, <code>depends on</code> and <code>see also</code> bug as appropriate.
* when bug is successfully created, ''needinfo'' request with a brief description of the reason for the request and provide relevant information.


== Checklist ==
== Checklist ==


* meta bugs created in Bugzilla?
* meta bugs created in Bugzilla?
*
* responsibilities for suites/subsuites divided amongst engineers (if multiple engineers assigned)?
* for each job, for each bug, associate an existing bug or create a new bug.
* for each bug created, has triage owner been notified with ''needinfo'' describing the nature of the problem?
75

edits

Navigation menu