New issue
Advanced search Search tips

Issue 759489 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

183.5% regression in v8.runtimestats.browsing_mobile at 495177:495292

Project Member Reported by tebbi@chromium.org, Aug 28 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 28 2017

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

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


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

android-nexus5

Comment 3 by tebbi@chromium.org, Aug 29 2017

 Issue 759488  has been merged into this issue.

Comment 4 Deleted

Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 29 2017


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8:gc:latency-mark-compactor_max/total:500ms_window:renderer_eqt:v8:gc:latency-mark-compactor_max


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 v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Aug 30 2017


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8:gc:latency-mark-compactor_max/total:500ms_window:renderer_eqt:v8:gc:latency-mark-compactor_max


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 v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Oct 24 2017


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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8:gc:latency-mark-compactor_max/total:500ms_window:renderer_eqt:v8:gc:latency-mark-compactor_max


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 v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Comment 10 by tebbi@chromium.org, Oct 27 2017

Status: WontFix (was: Assigned)
unreliable measure

Sign in to add a comment