[Webkit-unassigned] [Bug 138958] [meta] Run http tests parallel

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=138958

Csaba Osztrogonác <ossy at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ossy at webkit.org

--- Comment #2 from Csaba Osztrogonác <ossy at webkit.org> ---
(In reply to comment #1)
> I think that we are ready to flip the switch (at least on Mac), but I can't
> figure out which switch to flip.
> 
> There are still some failures when running with --fully-parallel, but they
> should not affect normal mode, as far as I can tell.

"-f, --fully-parallel - run all tests in parallel"

Ah, this help message is a little bit confusing.

Tests are sharded by subdirectories, leaf subdirectories are atomic 
and can't be distributed to different threads by default. Threads
pick up shards from the queue.

This fully parallel option disables sharding and each 
threads can pick up tests from the queue instead of shards.
I think we aren't ready for it yet, but it can reveal many
flakiness. It would be a good expetiment.

Back to parallel http test running. Now http and perf tests are considered as locked tests and locked tests run on 1 thread by default. You can easily override it with: --max-locked-shards command line option or WEBKIT_TEST_MAX_
LOCKED_SHARDS. (cmdline is the stronger one) The default option is defined to 1 in base.py in default_max_locked_shards. First we can override it for ports one by one. And then in base.py once it is stable everywhere. The ideal number would be the same as default_child_processes, but it depends on how much concurrent request can be served by the http server.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20141203/4e4c2cdf/attachment-0002.html>