New issue
Advanced search Search tips

Issue 919187 link

Starred by 2 users
Status: Assigned
Owner:
oysteine@chromium.org
Cc:
perezju@chromium.org
eseckler@chromium.org
vmi...@chromium.org
sadrul@chromium.org
ssid@chromium.org
charliea@chromium.org
crouleau@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Several rendering.desktop cases flaky on chromium.perf/mac-10_13_laptop_high_end-perf due to missing trace config metadata

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jan 4 
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@chromium.org

rendering.desktop/css_animations_simultaneous_updating_class and 3 other(s) in performance_test_suite failing on chromium.perf/mac-10_13_laptop_high_end-perf

Builders failed on: 
- mac-10_13_laptop_high_end-perf: 
  https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/mac-10_13_laptop_high_end-perf

Example log: (INFO) 2019-01-04 08:36:16,732 timeline_based_measurement._ComputeTimelineBasedMetrics:317  Starting to compute metrics on trace
(INFO) 2019-01-04 08:36:18,795 timeline_based_measurement._ComputeTimelineBasedMetrics:323  Processing resulting traces took 2.063 seconds
(ERROR) 2019-01-04 08:36:18,795 page_test_results.Fail:587  Failure recorded: MapFunctionError: Missing trace config metadata
    at validateTraceCategories (/b/s/w/ir/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:124:28)
    at runMetrics (/b/s/w/ir/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:59:7)
    at metricMapFunction (/b/s/w/ir/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:190:24)
    at Object.mapSingleTrace (/tracing/mre/map_single_trace.html:39:7)
    at eval (/b/s/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:61:18)
    at Object.runAndConvertErrorsToFailures (/tracing/mre/map_single_trace.html:24:10)
    at mapSingleTraceWithResult (/b/s/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:52:12)
    at Object.mapSingleTraceMain (/b/s/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:77:20)
    at eval (/b/s/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:90:15)
    at Object.loadHTMLFile (/b/s/w/ir/third_party/catapult/third_party/vinn/vinn/html_imports_loader.js:140:5)

Full log downloadable at https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/a510b261-1041-11e9-8e89-9810e8f40156

crouleau@, have you seen anything like this recently?

Comment 2 by charliea@chromium.org, Jan 4

Components: Speed>Benchmarks>Waterfall
Looks like this has also happened on rendering.mobile/linkedin_desktop_gpu_raster_2018 (run here: https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/Android%20Nexus6%20WebView%20Perf/3758, failure log here: https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/bb2b9bbe-1050-11e9-b9bf-0242ac110003)

Comment 3 by crouleau@chromium.org, Jan 5

Cc: crouleau@chromium.org ssid@chromium.org
Owner: benjhayden@chromium.org
Ben, can you please take a look at this?

https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/metrics/metric_map_function.html?q=metric_map_function.html&sq=package:chromium&dr&l=101

Comment 4 by crouleau@chromium.org, Jan 5

Cc: perezju@chromium.org
Looks like Juan make changes to this recently: https://chromium-review.googlesource.com/c/catapult/+/1387914 + Juan in case this could be a culprit

Comment 5 by benjhayden@chromium.org, Jan 5

Owner: oysteine@chromium.org
Hm, traces should have metadata. Oystein?

Comment 6 by perezju@chromium.org, Jan 7 

I don't think my changes should affect anything about tracing.

Comment 7 by johnchen@chromium.org, Today (10 hours ago) 

This issue is still persisting on builder mac-10_13_laptop_high_end-perf (https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/mac-10_13_laptop_high_end-perf). Every build has several failures from rendering.desktop cases, though the actual failures differ from build to build. The error messages are always the same as given in the original issue description.

Comment 8 by johnchen@chromium.org, Today (9 hours ago)

Labels: Type-Bug
Similar issues are also observed with rendering.mobile cases. For example,

Builder Android Nexus6 WebView Perf https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/Android%20Nexus6%20WebView%20Perf/3899 has two failures with the same error:

* rendering.mobile/google_news_ios (log https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/f6d51b54-1e74-11e9-b9e6-0242ac110004)

* rendering.mobile/new_tilings (log https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/0544e0d4-1e75-11e9-b9e6-0242ac110004)


Builder android-nexus5x-perf https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/android-nexus5x-perf/1413 has one failure with this error:

* rendering.mobile/css_animations_simultaneous_inline_style (log https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/43adf794-1e5b-11e9-922c-0242ac110002)

Comment 9 by crouleau@chromium.org, Today (9 hours ago)

Cc: sadrul@chromium.org vmi...@chromium.org
Components: Internals>GPU>Metrics

Comment 10 by oysteine@google.com, Today (9 hours ago) 

eseckler: Can you think of any reasons why "trace-config" metadata would still be missing, after the SMB scraping fix?

Comment 11 by johnchen@chromium.org, Today (8 hours ago)

Cc: eseckler@chromium.org
More flakiness observed on chromium.perf/mac-10_12_laptop_low_end-perf with the same error message. A few examples from flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=performance_test_suite&tests=rendering.desktop%2Fbouncing_balls_shadow%2C%20rendering.desktop%2Fcss_transitions_staggered_style_element%2C%20rendering.desktop%2Fhakim
►

Sign in to add a comment