Issue metadata
Sign in to add a comment
|
No data received for system_health.common_mobile from android-nexus5X since 479373 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975528752711513824
,
Jun 28 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.common_mobile Metric : load:energy_sum/background_media/background_media_imgur Revision Exit Code N chromium@479373 0 +- N/A 20 good chromium@479556 0 +- N/A 20 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=background.media.imgur system_health.common_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8975528752711513824 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5842794821713920 | 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!
,
Jun 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975524916099420176
,
Jun 28 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.common_mobile Metric : idle:power_avg/background_media/background_media_imgur Revision Exit Code N chromium@479373 0 +- N/A 20 good chromium@479556 0 +- N/A 20 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=background.media.imgur system_health.common_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8975524916099420176 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5213186975858688 | 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!
,
Jun 28 2017
This appears to be an infrastructure issue. Logs here (https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus5X_Perf%2F229%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.memory_mobile_on_Android%2F0%2Fstdout). AdbShellCommandFailedError: (device: 01d30cfd7bc7d319) shell command run via adb failed on the device: command: rm -f /data/local/chrome-trace-config.json Over to bot sheriff.
,
Jun 29 2017
Are we sure all of those are due to the same reason? A few of those I'm pretty sure are about disabled/removed stories. But it also looks like several unrelated things are being clustered together.
,
Jun 29 2017
Er, yeah, looks like I merged too aggressively. I'll split some of these up when I get the chance.
,
Jun 29 2017
From my end, it looks like all of the power-related data stoppages are due to stories being disabled/removed.
,
Jun 30 2017
So...wontfix? |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, Jun 28 2017