Issue metadata
Sign in to add a comment
|
archive_webkit_results is very slow |
||||||||||||||||||||||||
Issue descriptionTake https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng/builds/271196/steps/archive_webkit_tests_results for example (though it's far from the only one) As of this writing, it has been running for 18 minutes and is not yet done. This compares with a webkit_tests step which took 33 minutes. Uploading the result takes more than half the time of running the tests! Surely there's a way to optimize that? I find that usually the bots with the layout tests are on the critical path to getting my CL landed, so this is would be very useful for me.
,
Sep 1 2016
,
Oct 18 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tandrii@chromium.org
, Aug 13 2016Components: -Infra>CQ Infra>Client>Chrome
Status: Untriaged (was: Unconfirmed)