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

Issue 718907 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
█ kraynov@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.5% regression in page_cycler_v2.tough_layout_cases at 468565:468595

Project Member Reported by kraynov@chromium.org, May 5 2017 
See the link to graphs below.

Comment 1 by kraynov@chromium.org, May 5 2017 

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

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


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

chromium-rel-win7-gpu-intel
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, May 5 2017 


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___bookish.com

Revision             Result                  N
chromium@468564      441.414 +- 49.8755      21      good
chromium@468595      439.271 +- 12.137       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...bookish.com page_cycler_v2.tough_layout_cases

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

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


| 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 6 by 42576172...@developer.gserviceaccount.com, May 5 2017 


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___bookish.com

Revision             Result                  N
chromium@468564      435.067 +- 14.2921      21      good
chromium@468595      435.2 +- 15.6334        21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...bookish.com page_cycler_v2.tough_layout_cases

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

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


| 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 8 by 42576172...@developer.gserviceaccount.com, May 5 2017 


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___bookish.com

Revision             Result                  N
chromium@468564      436.408 +- 17.6059      21      good
chromium@468595      435.536 +- 16.7592      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...bookish.com page_cycler_v2.tough_layout_cases

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

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


| 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 9 by 42576172...@developer.gserviceaccount.com, May 5 2017 


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___bookish.com

Revision             Result                  N
chromium@468564      453.405 +- 14.5839      20      good
chromium@468595      452.582 +- 18.6057      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...bookish.com page_cycler_v2.tough_layout_cases

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

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


| 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!

Comment 10 by benhenry@chromium.org, Jul 27 2017

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