New issue
Advanced search Search tips

Issue 742744 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
simonhatch@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

False blaming by perf bots

Project Member Reported by battre@chromium.org, Jul 14 2017 
I was blamed for a 10% regression in system_health.memory_mobile here https://bugs.chromium.org/p/chromium/issues/detail?id=741748#c3

However, the blamed CL
1) Only moves code from one location to another (feature-neutral refactoring).
2) Is probably not even linked into the binary that is tested.

Can we retrigger the bisect?

Comment 1 by pmeenan@chromium.org, Jul 14 2017

Status: (was: Available)
No need to file a separate bug just to re-run the bisect, we can do that off of the regression alert.  Leaving this as available in case the speed-infra team wants to investigate but it looks like it may be a noisy benchmark and not an issue with the bisect itself.  I'll add the benchmark owner to the alert as well.

Comment 2 by pmeenan@chromium.org, Jul 14 2017

Owner: ----
Status: Available

Comment 3 by perezju@chromium.org, Jul 14 2017

Status: WontFix (was: Available)
Agree, we can follow this up on issue 741748.
►

Sign in to add a comment