Using this form to request a customized field instead of a label.

This customized field is for Findit, a culprit finder for Chrome (https://sites.google.com/a/chromium.org/cr-culprit-finder/findit/). Findit files bugs for flaky tests, and will use this customized field for querying duplicates.

FlakyTest > (str) TestNmae

1] Customized Field Name: FlakyTest

Guideline 1: Unless a hierarchy of labels is needed, please avoid creating
new root parents.
Guideline 2: Proj(ects) labels should be used for efforts that have a clear
start/ end
Guideline 3: Hotlist labels should be used for tracking on-going efforts
across multiple components (e.g. Hotlist-GoodFirstBug)
Guideline 4: Due to the way auto-complete works we avoid using hyphens to
express anything other than hierarchy (e.g. UI-Browser-Omnibox).  We use
CamelCase to represent multiple words (e.g. Hotlist-CamelCase versus
Hotlist-Camel-Case).


2] Parent Label (e.g. Proj-, Hotlist-, etc...): N/A

Note: We generally avoid creating new component namespaces, unless there is
a new hierarchy that needs to be expressed.  Please try and use existing
label as parents.

3] Description of Customized Field: This will track the name of the test that's flaky. The bug that this field is set on will be one that's filed for this flaky test.  

4] Please specify what triage practices will be followed for the label
(i.e. what team will do it and how frequently).

chrome-findit@ will be responsible for all bugs under this category as well as any sheriffs that are triaging the flaky tests.



 

Using this form to request a customized field instead of a label.

This customized field is for Findit, a culprit finder for Chrome (https://sites.google.com/a/chromium.org/cr-culprit-finder/findit/). Findit files bugs for flaky tests, and will use this customized field for querying duplicates.

FlakyTest > (str) TestNmae

1] Customized Field Name: FlakyTest

Guideline 1: Unless a hierarchy of labels is needed, please avoid creating
new root parents.
Guideline 2: Proj(ects) labels should be used for efforts that have a clear
start/ end
Guideline 3: Hotlist labels should be used for tracking on-going efforts
across multiple components (e.g. Hotlist-GoodFirstBug)
Guideline 4: Due to the way auto-complete works we avoid using hyphens to
express anything other than hierarchy (e.g. UI-Browser-Omnibox).  We use
CamelCase to represent multiple words (e.g. Hotlist-CamelCase versus
Hotlist-Camel-Case).


2] Parent Label (e.g. Proj-, Hotlist-, etc...): Test-

Note: We generally avoid creating new component namespaces, unless there is
a new hierarchy that needs to be expressed.  Please try and use existing
label as parents.

3] Description of Customized Field: This will track the name of the test that's flaky. The bug that this field is set on will be one that's filed for this flaky test.  

4] Please specify what triage practices will be followed for the label
(i.e. what team will do it and how frequently).

Findit will file all such bugs under this category and pass over to Chromium Sheriffs Queue to further triage the flaky tests.



 

Using this form to request a customized field instead of a label.

This customized field is for Findit, a culprit finder for Chrome (https://sites.google.com/a/chromium.org/cr-culprit-finder/findit/). Findit files bugs for flaky tests, and will use this customized field for querying duplicates.

Test-Flaky > (str) TestNmae

1] Customized Field Name: Flaky

Guideline 1: Unless a hierarchy of labels is needed, please avoid creating
new root parents.
Guideline 2: Proj(ects) labels should be used for efforts that have a clear
start/ end
Guideline 3: Hotlist labels should be used for tracking on-going efforts
across multiple components (e.g. Hotlist-GoodFirstBug)
Guideline 4: Due to the way auto-complete works we avoid using hyphens to
express anything other than hierarchy (e.g. UI-Browser-Omnibox).  We use
CamelCase to represent multiple words (e.g. Hotlist-CamelCase versus
Hotlist-Camel-Case).


2] Parent Label (e.g. Proj-, Hotlist-, etc...): Test-

Note: We generally avoid creating new component namespaces, unless there is
a new hierarchy that needs to be expressed.  Please try and use existing
label as parents.

3] Description of Customized Field: This will track the name of the test that's flaky. The bug that this field is set on will be one that's filed for this flaky test.  

4] Please specify what triage practices will be followed for the label
(i.e. what team will do it and how frequently).

Findit will file all such bugs under this category and pass over to Chromium Sheriffs Queue to further triage the flaky tests.