New issue
Advanced search Search tips

Issue 667418 link

Starred by 0 users

Issue metadata

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



Sign in to add a comment

11% regression in page_cycler_v2_site_isolation.basic_oopif at 432301:432475

Project Member Reported by mustaq@chromium.org, Nov 21 2016

Issue description

See the link to graphs below.
 

Comment 1 by mustaq@chromium.org, Nov 21 2016

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

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


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

chromium-rel-win8-dual
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Nov 22 2016


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@432300  484.55   50.1115  8  good
chromium@432475  518.681  6.20463  8  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 667418

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.nationalgeographic.com. page_cycler_v2_site_isolation.basic_oopif
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.nationalgeographic.com_
Relative Change: 7.04%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2279
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995357794318379184


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6584734509957120

| 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 Tests>AutoBisect.  Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 22 2016


===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@432300  489.291  124.232  27  good
chromium@432475  513.544  72.6793  27  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 667418

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.nationalgeographic.com. page_cycler_v2_site_isolation.basic_oopif
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.nationalgeographic.com_
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2280
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995272519695506256


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5773682985664512

| 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 Tests>AutoBisect.  Thank you!
Status: WontFix (was: Untriaged)
Recovered.

Sign in to add a comment