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

Issue 713097 link

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



Sign in to add a comment

44.7% regression in page_cycler_v2.tough_layout_cases at 464852:464856

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

Comment 1 by alexclarke@chromium.org, Apr 19 2017 

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

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


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

android-nexus6
Project Member

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


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___natunkantha.com

Revision             Result                  N
chromium@464851      1434.3 +- 1112.43       21      good
chromium@464856      1416.86 +- 1068.28      21      bad

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

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

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


| 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 19 2017 


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___natunkantha.com

Revision             Result                  N
chromium@464851      1428.37 +- 1263.98      21      good
chromium@464856      1286.12 +- 825.415      21      bad

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

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

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


| 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 7 by 42576172...@developer.gserviceaccount.com, Apr 20 2017 


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___natunkantha.com

Revision             Result                  N
chromium@464851      1412.15 +- 1117.32      21      good
chromium@464856      1378.81 +- 1069.82      21      bad

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

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

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


| 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, Apr 27 2017 


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___natunkantha.com

Revision             Result                  N
chromium@464851      1432.44 +- 909.8        21      good
chromium@464856      1502.81 +- 1072.91      21      bad

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

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

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


| 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