Needs-TestConfirmation

[David Grogan]

Does Needs-TestConfirmation actually work? There are many bugs, e.g. https://crbug.com/1418534, that have had that label for weeks without the Test team doing anything.

Below is my proposal to skip that label during triaging, but that only makes sense if the label is not ignored.

In "Task 2: Handling Component=UI issues", there's a link for the issues we should triage:

> Component=UI -Needs=Feedback -Type=Feature,Task

Can we also exclude Needs-TestConfirmation issues? I.e. change the above search query to:

> Component=UI -Needs=Feedback,TestConfirmation -Type=Feature,Task

-David (first time triager)

[Dave Tapuska]

I only see two bugs with the second link you provided. The first link (1418534) shouldn't be in our triage list because it doesn't have component=Blink

--
You received this message because you are subscribed to the Google Groups "Component:Blink bug rotation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crblink-rotati...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/crblink-rotation/202e5a89-acfd-41da-98c1-5bbdba7624d9n%40chromium.org.

[David Grogan]

Yeah, it has only two bugs because I just finished triaging. And it's the Component=UI issues, not the Component=Blink issues.

[Johnny Stenback]

+Vivian Zhi who might have insight into exactly what labels trigger what on the testing team's end.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/crblink-rotation/CAOZbSt3qBEe%3D2uoBzxY%2BAQj8z7ghn_6NzQJGpCC7hQyYHTOTkw%40mail.gmail.com.

[Vivian Zhi (支文文）]

+Christine A. Wang who owns Android only bug triage

by viewing this bug, this one did not get picked up by the triage team because we don't perform advanced bug triage like bug reproducing or bisecting for P3 issue. P3 bugs onl;y go through initial bug bucketing to assign to the right component, and if it is a regression , it get re-evaluate and possible boost up in priority ,but if a bug is reported by chromium contributor and mark as P3, we assume this is indeed a P3, so it will not get reproduced or bisected properly.