New issue
Advanced search Search tips

Issue 792913 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
npm@chromium.org
dproy@chromium.org
tdres...@chromium.org
sullivan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

25.4% regression in system_health.common_desktop at 521278:521304

Project Member Reported by npm@chromium.org, Dec 7 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 7 2017 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=792913

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=4dd318676b244e86d035ad1f269872cb3923522b00b6f80324baf9cae64c696e


Bot(s) for this bug's original alert(s):

chromium-rel-win10
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 7 2017 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/1480bf6c040000
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Dec 7 2017 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/15d27304040000
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Dec 7 2017 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14fc88d4040000
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Dec 7 2017 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12ece574040000

Comment 10 by npm@chromium.org, Dec 7 2017 

Added to go/bad-bisects because the graph looks like a clear regression but pinpoint didn't catch it.

Comment 11 by sullivan@chromium.org, Jan 22 2018

Cc: tdres...@chromium.org sullivan@chromium.org
Status: WontFix (was: Untriaged)
Too noisy, bisect can't repro. +tdresser FYI: I'm in the backlog for December/November, and EQT metrics are noisy. Did this get looked at already?

Comment 12 by tdres...@chromium.org, Jan 22 2018

Cc: dproy@chromium.org
Nope, we haven't addressed this.
We should probably switch this to n'th percentile QT, instead of max of a sliding window.

Deep, could you add that to your backlog?

Comment 13 by tdres...@chromium.org, Jan 22 2018 

Oh, bug is here:
https://github.com/catapult-project/catapult/issues/3356

This is due to noise in TTI, which we're hoping to address soon (TM).
We'll follow up once we're done our current TTI investigation.
►

Sign in to add a comment