[Webkit-unassigned] [Bug 88134] new-run-webkit-tests should spin-up enough httpd processes to avoid timeouts

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jun 1 15:05:27 PDT 2012


Dirk Pranke <dpranke at chromium.org> changed:

           What    |Removed                     |Added
         AssignedTo|webkit-unassigned at lists.web |dpranke at chromium.org
                   |kit.org                     |

--- Comment #8 from Dirk Pranke <dpranke at chromium.org>  2012-06-01 15:05:26 PST ---
I think it makes sense to bump up StartServers to some smallish N * floor(--max-locked-shards, --child-processes) (since that controls the number of concurrent HTTP tests), since I agree it's likely there is more than one http request in flight per test. I have definitely seen the initial timeout issues on Linux (although, oddly, only on Linux). If that would solve the timeout issues then perhaps we could also increase the default -max-locked-shards beyond one, since that would be a big win on the bigger multicore machines.

I will play around with some approaches and post something.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list