Issue metadata
Sign in to add a comment
|
No data received for smoothness.top_25_smooth first_gesture_scroll_update_latency on several bots |
||||||||||||||||||||
Issue descriptionSeeing this on several android and windows bots. Can't see any obvious change in the commit ranges. Tim, can you take a look?
,
Aug 5 2016
Sample log: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%207%20x64%20Perf%20%283%29/builds/4564/steps/smoothness.top_25_smooth/logs/stdio [ RUN ] ESPN (INFO) 2016-08-05 05:06:44,026 cache_temperature.EnsurePageCacheTemperature:55 PageCacheTemperature: any (INFO) 2016-08-05 05:06:44,104 chrome_tracing_agent._CreateTraceConfigFile:263 Trace config file string: {"trace_config": {"included_categories": ["webkit.console", "benchmark", "blink.console", "trace_event_overhead"], "record_mode": "record-as-much-as-possible"}} (INFO) 2016-08-05 05:06:44,104 tracing_backend.StartTracing:133 Start Tracing Request: {'params': {'transferMode': 'ReturnAsStream', 'traceConfig': {'recordMode': 'recordAsMuchAsPossible', 'includedCategories': ['webkit.console', 'benchmark', 'blink.console', 'trace_event_overhead']}}, 'method': 'Tracing.start'} (INFO) 2016-08-05 05:06:47,448 trace._GetTempFileHandle:65 Trace (TraceDataPart("traceEvents")) of size 713188 bytes saved. (INFO) 2016-08-05 05:06:47,448 trace._GetTempFileHandle:65 Trace (TraceDataPart("tabIds")) of size 40 bytes saved. (INFO) 2016-08-05 05:06:47,448 trace._GetTempFileHandle:65 Trace (TraceDataPart("telemetry")) of size 880 bytes saved. (WARNING) 2016-08-05 05:06:52,686 model._CreateImporters:275 No importer found for TraceDataPart("telemetry") [ OK ] ESPN (8769 ms) Sample trace: https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/trace-file-id_14-2016-08-05_05-08-56-91968.html
,
Aug 5 2016
Cl range: 405408:405433 I kicked off a mean bisect, since the return code is always 0, we'll see if we can get any info in the output.
,
Aug 5 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005162277129928192
,
Aug 5 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005162268637748512
,
Aug 5 2016
I don't see anything suspicious in the CL range. Looks like there are distinct ranges here though. 406555 - 407834 contains another data stoppage, I started a return code and a mean bisect for this case.
,
Aug 5 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@406555 6.38803 0.0 1 good Bisect job ran on: android_nexus9_perf_bisect Bug ID: 634897 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.key_mobile_sites_smooth Test Metric: mean_input_event_latency/mean_input_event_latency Relative Change: None Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1980 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005162268637748512 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5842346348904448 | 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 Tests>AutoBisect. Thank you!
,
Aug 5 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005152528286889152
,
Aug 5 2016
===== BISECT JOB RESULTS ===== Status: failed ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@406555 6.38803 0.0 1 good Bisect job ran on: android_nexus9_perf_bisect Bug ID: 634897 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.key_mobile_sites_smooth Test Metric: mean_input_event_latency/mean_input_event_latency Relative Change: None Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1980 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005162268637748512 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5842346348904448 | 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 Tests>AutoBisect. Thank you!
,
Aug 5 2016
===== BISECT JOB RESULTS ===== Status: completed ===== TESTED REVISIONS ===== Revision Exit Code Std Dev N Good? chromium@406555 0 N/A 20 good chromium@407834 0 N/A 20 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 634897 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.key_mobile_sites_smooth Test Metric: mean_input_event_latency/mean_input_event_latency Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1979 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005162277129928192 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5775894614900736 | 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 Tests>AutoBisect. Thank you!
,
Aug 10 2016
,
Sep 30 2016
This has recovered. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sullivan@chromium.org
, Aug 5 2016