New issue
Advanced search Search tips

Issue 778107 link

Starred by 0 users

Issue metadata

Status: Assigned
Owner:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Regressed on one metric, improved on another

Project Member Reported by jchin...@chromium.org, Oct 25 2017

Issue description

Testing bug.
 

Comment 1 Deleted

Comment 3 Deleted

Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Oct 25 2017


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

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


Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : total:500ms_window:renderer_eqt:v8:gc:full-mark-compactor_max/total:500ms_window:renderer_eqt:v8:gc:full-mark-compactor_max


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection
Status: Assigned (was: Untriaged)

Sign in to add a comment