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

Issue 700979 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

35.5% regression in startup.warm.blank_page at 454978:455037

Project Member Reported by hjd@chromium.org, Mar 13 2017

Issue description

See the link to graphs below.
 

Comment 1 by hjd@chromium.org, Mar 13 2017

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglJ_QjQgM


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

chromium-rel-win7-gpu-intel
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 13 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : first_main_frame_load_time/first_main_frame_load_time

Revision             Result                  N
chromium@454977      116.524 +- 7.69663      21      good
chromium@455037      117.762 +- 18.4339      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=2 --also-run-disabled-tests startup.warm.blank_page

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8985216906613441216

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5239983423619072


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Apr 11 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : first_main_frame_load_time/first_main_frame_load_time

Revision             Result                  N
chromium@454977      128.952 +- 194.82       21      good
chromium@455037      117.857 +- 6.82433      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=2 --also-run-disabled-tests startup.warm.blank_page

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982647706366085360

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5239983423619072


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Status: WontFix (was: Untriaged)
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.

Sign in to add a comment