New issue
Advanced search Search tips

Issue 896850 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 894744
Owner: ----
Closed: Oct 18
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

startup.mobile/intent:(coldish|warm):bbc in performance_test_suite failing on chromium.perf/Android Nexus5 Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Oct 18

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of sullivan@google.com

loading.mobile/TribunNews_3g and 4 other(s) in performance_test_suite failing on chromium.perf/Android Nexus5 Perf

Builders failed on: 
- Android Nexus5 Perf: 
  https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/Android%20Nexus5%20Perf


 
No screenshot from telemetry. Sample logs: https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/cf3ae9a4-d2ff-11e8-ac7c-0242ac110008

(INFO) 2018-10-18 17:58:27,227 timeline_based_measurement._ComputeTimelineBasedMetrics:323  Processing resulting traces took 4.669 seconds
(ERROR) 2018-10-18 17:58:27,227 page_test_results.Fail:540  Failure recorded: TraceImportError: No clock sync markers exist pairing clock domain "LINUX_FTRACE_GLOBAL" with target clock domain "LINUX_CLOCK_MONOTONIC".
    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:350: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)


Looking at flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=performance_test_suite&showAllRuns=true&builder=chromium.perf%3AAndroid%20Nexus5%20Perf

These started failing at  r598310:r598362. Kicking off a bisect and disabling.
Mergedinto: 894744
Status: Duplicate (was: Available)
Looks like this is already being looked into in  bug 894744 , but the disable CL on that bug was incorrect. Duping and fixing the disable.
Cc: pasko@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/100ae57ae40000

startup.mobile benchmark: enable atrace temporarily by pasko@chromium.org
https://chromium.googlesource.com/chromium/src/+/973cf57b1f0da5d6833b680b0b8efe8c6337eed6
Failure rate: 0.1 → 1 (+0.9)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None

Sign in to add a comment