New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 636560 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 310382
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

archive_webkit_results is very slow

Project Member Reported by cbiesin...@chromium.org, Aug 10 2016

Issue description

Take 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.
 
Cc: dpranke@chromium.org tansell@chromium.org
Components: -Infra>CQ Infra>Client>Chrome
Status: Untriaged (was: Unconfirmed)
Status: Available (was: Untriaged)

Comment 3 by tkent@chromium.org, Oct 18 2016

Mergedinto: 310382
Status: Duplicate (was: Available)

Sign in to add a comment