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

Issue 766524 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

20.2%-389.8% regression in loading.desktop at 495063:502320

Project Member Reported by alexclarke@chromium.org, Sep 19 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 19 2017 

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

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


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

chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 19 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/Walgreens


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Walgreens loading.desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8968031281220799168


For feedback, file a bug with component Speed>Bisection

Comment 4 by benhenry@chromium.org, Dec 12 2017

Status: WontFix (was: Untriaged)
Bisect unable to find culprit, this regression exists in stable. Ignoring.
►

Sign in to add a comment