New issue
Advanced search Search tips

Issue 891268 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11.1% regression in power.desktop at 595074:595103

Project Member Reported by tdres...@chromium.org, Oct 2

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=891268

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


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

mac-10_13_laptop_high_end-perf

power.desktop - Benchmark documentation link:
  https://bit.ly/power-benchmarks
Cc: estevenson@chromium.org
Owner: estevenson@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1004d4c2e40000

[size trybot] Filter guidance for non-regressions. by estevenson@chromium.org
https://chromium.googlesource.com/chromium/src/+/f4097091174e94e2b7f996147fbc49da49d3ada4
0.07457 → No values

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/power-benchmarks
Owner: ----
Status: Untriaged (was: Assigned)
The suggested culprit CL only modifies a test script.

Sign in to add a comment