Issue metadata
Sign in to add a comment
|
power.idle_platform failing on android due to clock sync error |
||||||||||||||||||||
Issue descriptionpower.idle_platform failing on multiple builders Builders failed on: - Android Nexus6 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20Perf - Android Nexus7v2 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf - Android One Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf - Win 7 x64 Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20x64%20Perf Unexpected Failures: * power.idle_platform/IdleStory_10s * power.idle_platform/IdleStory_120s * power.idle_platform/IdleStory_60s https://chromium-swarm.appspot.com/task?id=3925a2226511ee10&refresh=10&show_raw=1 (INFO) 2017-10-11 19:29:50,301 cmd_helper._ValidateAndLogCommand:160 [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s ZX1G22KCC9 shell '( echo -n /proc/[0-9]*/task/[0-9]* );echo %$?' (INFO) 2017-10-11 19:29:50,440 trace_data.Serialize:191 Trace sizes in bytes: {'systemTraceEvents': 730, 'telemetry': 3948} (WARNING) 2017-10-11 19:29:55,219 timeline_based_measurement._ComputeTimelineBasedMetrics:331 Processing resulting traces took 1.020 seconds These categories are unavailable: rs binder_driver Traceback (most recent call last): File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/value/failure.py", line 41, in _GetExcInfoFromMessage raise Exception(message) Exception: TraceImportError: No clock sync markers exist pairing clock domain "LINUX_FTRACE_GLOBAL" with target clock domain "TELEMETRY". at ClockSyncManager.getTimeTransformerRaw_ (/tracing/model/clock_sync_manager.html:176:15) at ClockSyncManager.getModelTimeTransformer (/tracing/model/clock_sync_manager.html:159:19) at FTraceImporter.importEvents (/tracing/extras/importer/linux_perf/ftrace_importer.html:349:40) at importer (/tracing/importer/import.html:198:65) at task.subTask (/tracing/importer/import.html:145:32) at Task.run (/tracing/base/task.html:80:50) at Function.Task.RunSynchronously (/tracing/base/task.html:125:25) at Import.importTraces (/tracing/importer/import.html:74:17) at createModelFromTraceData (/b/swarming/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:38:9) at eval (/b/swarming/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:57:25) [ FAILED ] IdleStory_120s (135272 ms)
,
Oct 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8965975781701505616
,
Oct 12 2017
My guess is its this cl: https://chromium-review.googlesource.com/c/catapult/+/705273/3/telemetry/telemetry/internal/story_runner.py This problem would have also been caused by this cl I just landed today: https://chromium-review.googlesource.com/c/chromium/src/+/710215 I will revert both CLs.
,
Oct 12 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : power.idle_platform Metric : benchmark_duration/benchmark_duration Revision Exit Code N chromium@507372 1 +- N/A 20 good chromium@507447 1 +- 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=IdleStory_10s power.idle_platform More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8965975781701505616 For feedback, file a bug with component Speed>Bisection
,
Oct 12 2017
It looks like the windows failure is unrelated (just timing out). The android failures are a problem with the clock sync missing between atrace and telemetry. Renaming bug to reflect that fact. I will disable this benchmark (referencing this bug) on the given android platforms and reland my CLs to remove ShouldDisable.
,
Oct 12 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7bfc0c4bb5ec991deda375c439712caf9ba07ce8 commit 7bfc0c4bb5ec991deda375c439712caf9ba07ce8 Author: rnephew <rnephew@chromium.org> Date: Thu Oct 12 20:57:36 2017 [Telemetry] Disable power.idle_platform on failing android platforms. They are failing because of a clock sync issue where a clock sync path between ftrace and telemetry cannot be found. Bug: 773949 Change-Id: I4823387051b644fd198bf619abc6205d628f89fd Reviewed-on: https://chromium-review.googlesource.com/716559 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: rnephew <rnephew@chromium.org> Cr-Commit-Position: refs/heads/master@{#508459} [modify] https://crrev.com/7bfc0c4bb5ec991deda375c439712caf9ba07ce8/tools/perf/benchmarks/power.py
,
Jun 18 2018
Closing this as WontFix, as the revert was required for stability anyhow |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ashleymarie@chromium.org
, Oct 12 2017