Significant cycle time regressions across webkit_layout_test-related steps |
||||
Issue descriptionRuntimes for webkit_layout_tests and archive_webkit_tests_results spiked overnight starting between 2017-11-09T04:00:00Z and 2017-11-09T06:00:00Z. This spanned OSes: - linux_chromium_rel_ng: http://shortn/_LfS3tWSBl3 - mac_chromium_rel_ng: http://shortn/_9PyTIyPuz0 - win7_chromium_rel_ng: http://shortn/_vsOPIvuD5M Swarming task time for webkit_layout_tests increased modestly around the same time.
,
Nov 9 2017
It's the UKM stderr thing again.
,
Nov 9 2017
Suspected CL is https://chromium-review.googlesource.com/c/chromium/src/+/757885. Revert is in the CQ.
,
Nov 9 2017
stderr contains the following: [5416:2284:1109/072808.502:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_renderer from binding interface: ukm::mojom::UkmRecorderInterface exposed by: content_browser [5416:2284:1109/072808.714:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_renderer from binding interface: ukm::mojom::UkmRecorderInterface exposed by: content_browser
,
Nov 9 2017
Hi, John. Do you think this is likely to be the same issue as crbug.com/783247 "archive_webkit_tests_results failing on multiple builders"? Thanks!
,
Nov 9 2017
I am curious: could a change like 757885 affect "archive_webkit_tests_results"? I naively think that archiving step doesn't run any layout tests, instead it just zips things and stores the result somewhere.
,
Nov 9 2017
Yeah, it results in a massively increased number of files that we have to archive. The same thing happened in https://chromium-review.googlesource.com/c/chromium/src/+/722301, the previous attempt to land the same CL.
,
Nov 9 2017
re "massively increased": I downloaded one of the archives & see over 61000 stderr files matching #4.
,
Nov 9 2017
,
Nov 9 2017
Ah, that makes good sense! Thanks for explanation!
,
Nov 9 2017
I'm really sorry and thank you for treating this. Now my culprit CL was reverted, the problem was fixed?
,
Nov 9 2017
#11: no worries. It should be, but I'm still waiting on post-revert data to make it into our monitoring.
,
Nov 9 2017
2hr metrics are returning to their previous levels: http://shortn/_2eOTKGYsdp |
||||
►
Sign in to add a comment |
||||
Comment 1 by dpranke@chromium.org
, Nov 9 2017