New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 623995 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
dtu@chromium.org
creis@chromium.org
█ aiolos@chromium.org
simonhatch@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Unclear who to contact when Perf regression bisect is wrong

Project Member Reported by creis@chromium.org, Jun 28 2016 
Perf regression bugs are automatically assigned based on the results of the bisect, but there are false positives when the bisect points to a revision that couldn't have caused the regression.  There's no information in the bug or the FAQ (http://www.chromium.org/developers/speed-infra/perf-bug-faq) for how the owner in the bug should respond in this case.

Should the bug be left ownerless?  Marked WontFix?  Marked Needs-Bisect?  Assigned to someone else on the Perf team for triage?

(Example:  issue 623831 .)

Comment 1 by sullivan@chromium.org, Jun 28 2016

Cc: aiolos@chromium.org dtu@chromium.org
It's fine to:
1) Click the "Not what you expected?" link
2) Add a comment explaining it's not your CL
3) Leave the bug ownerless (it's triaged by rotation)

I'm leaving this open since ideally the bisect bot's comment would explain the process better, and probably automate it (you click the "Not what you expected" link and it sets owner appropriately)

Comment 2 by creis@chromium.org, Jun 28 2016 

Hmm, I get "No permission" when I click that link.

Comment 3 by benhenry@chromium.org, Feb 3 2017

Components: Speed>Bisection
►

Sign in to add a comment