New issue
Advanced search Search tips

Issue 740143 link

Starred by 1 user
Status: Duplicate
Merged: issue 724262
Owner:
simonhatch@chromium.org
Closed: Jul 2017
Cc:
nedngu...@google.com
u...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

We have 35 inactive bugs for v8.infinite_scroll_tbmv2

Project Member Reported by mustaq@chromium.org, Jul 7 2017 
Do we care about this benchmark, given that it has no owners? How long do we want to continue like this?

Here is the list of open regressions:
https://bugs.chromium.org/p/chromium/issues/list?can=2&q=v8.infinite_scroll_tbmv2&sort=status

I spotted one ( Issue 718039 ) which has received no new data points in two months.

Comment 1 by sullivan@chromium.org, Jul 7 2017

Cc: nedngu...@google.com u...@chromium.org
If you look at go/chrome-benchmarks, the owner is ulan@. Part of the problem here is that the dashboard doesn't automatically cc owners on bugs, which we're working on in Q3.

Comment 2 by nedngu...@google.com, Jul 7 2017 

I am working on removing the v8.infinite_scroll* benchmarks:  issue 724262

Comment 3 by mustaq@chromium.org, Jul 7 2017

Mergedinto: 724262
Status: Duplicate (was: Untriaged)

Comment 4 by u...@chromium.org, Jul 11 2017 

We do care about this benchmark. Alerts go to V8 memory sheriff rotation.

The untriaged bugs in the list were created by people outside V8 memory sheriff rotation. I don't know why that happened.

Comment 5 by nedngu...@google.com, Jul 11 2017

Owner: simonhatch@chromium.org
+Simon for alert config

Comment 6 by u...@chromium.org, Jul 11 2017 

I assigned all untriaged bugs from the list to myself.

Comment 7 by simonhatch@chromium.org, Jul 11 2017 

What needs to be done for the alert config?

Comment 8 by nedngu...@google.com, Jul 11 2017 

Seems like for some reason, the alert of v8.infinite_scroll_tbmv2 go to perf sheriffs instead of v8 sheriffs.

That bug may be irrelevant now that we turn down this benchmark & rely on v8.browsing_* for coverage ( issue 724262 )

Comment 9 by simonhatch@chromium.org, Jul 11 2017 

Ok, if they're being turned down I'll leave this for now.
►

Sign in to add a comment