Issue metadata
Sign in to add a comment
|
No data received for system_health.common_desktop from linux-release since 480053 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975432266164326224
,
Jun 29 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: linux_perf_bisect Benchmark : system_health.common_desktop Metric : cpu_time_percentage_avg/browse_social/browse_social_tumblr_infinite_scroll Revision Exit Code N chromium@480053 0 +- N/A 20 good chromium@480179 0 +- N/A 20 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.tumblr.infinite.scroll system_health.common_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8975432266164326224 For feedback, file a bug with component Speed>Bisection
,
Jun 30 2017
,
Jul 4 2017
remove Performance-Loading label since this looks an infra issue rather than a regression that loading team should investigate.
,
Aug 18 2017
We stopped support for data stoppage alerts. This was likely caused by some recent linux outages. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, Jun 29 2017