Issue metadata
Sign in to add a comment
|
v8.runtimestats.browsing_desktop failing on 5 builders |
||||||||||||||||||
Issue descriptionv8.runtimestats.browsing_desktop failing on 5 builders browse:news:reddit is failing. Builders failed on: - Mac Retina Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%20Retina%20Perf - Win 10 High-DPI Perf: https://build.chromium.org/p/chromium.perf/builders/Win%2010%20High-DPI%20Perf - Win 10 Perf: https://build.chromium.org/p/chromium.perf/builders/Win%2010%20Perf - Win 7 Nvidia GPU Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20Nvidia%20GPU%20Perf - Win 8 Perf: https://build.chromium.org/p/chromium.perf/builders/Win%208%20Perf
,
Sep 1 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: winx64_10_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : benchmark_duration/benchmark_duration Revision Exit Code N chromium@498035 1 +- N/A 20 good chromium@498100 1 +- N/A 20 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 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/8969739681003908304 For feedback, file a bug with component Speed>Bisection
,
Sep 7 2017
The consistent failure that we were seeing when this bug was opened has since been resolved, so I'm going to go ahead and close this. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 31 2017