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

Issue 610690 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Oct 4
Cc:
█ robert...@chromium.org
█ pras...@chromium.org
dtu@chromium.org
█ eakuefner@chromium.org
█ aiolos@chromium.org
simonhatch@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

return_code bisect dupes to perf regression bugs

Project Member Reported by sullivan@chromium.org, May 10 2016 
Example:  bug 610338 

A return_code bisect was kicked off for the failing test, and it turns out that the culprit CL also caused performance regressions. The bisect duped the test failure bug against the performance regression bug.

In my opinion, return_code bisects should not dupe bugs at all:
 * Perf regression bugs shouldn't be duped into return_code bisects
 * return_code bisects shouldn't dupe the bugs even if there are two return_code bugs with the same culprits, because the test re-enables are tracked in two separate bugs and one re-enable may be overlooked if they are duped.

I think the relevant code is here: https://github.com/catapult-project/catapult/blob/master/dashboard/dashboard/update_bug_with_results.py#L249

Anyone want to take a look at this? I'd be happy to provide guidance/review.

Comment 1 by pras...@chromium.org, May 23 2016

Status: Available (was: Untriaged)
This is good starter bug to work on updating bisect results on issues.

Comment 2 by benhenry@google.com, Feb 2 2017

Components: Speed>Dashboard
Labels: -Performance-Dashboard

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

Components: Speed>Bisection
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 13 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by benjhayden@chromium.org, Oct 4

Status: Archived (was: Untriaged)
►

Sign in to add a comment