[Webkit-unassigned] [Bug 46453] [NRWT] Put the http and websocket tests to end of the test list

[bugzilla-daemon at webkit.org]

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





--- Comment #5 from Tony Chang <tony at chromium.org>  2010-09-24 14:30:54 PST ---
(In reply to comment #4)
> Because when we start more than one NRWT on the same machine and there is an http lock it can starts with the other tests so it just blocks when reaches the http tests.
> So if this slows the NRWT I can put the --wait-for-httpd switch to this patch and when its not enable it will put the http tests to the begin of the queue.

With NRWT, if you're running with multiple threads, won't only the http thread block?  For example:

first NRWT
  a) first thread running http tests
  b) second thread running some other tests

second NRWT
  c) first thread blocks on http tests in first NRWT
  d) second thread running some other tests

So only a single thread will block on the second NRWT.  All the other tests can be run by thread (d) while thread (c) is blocking.  Maybe I don't understand how http locking is implemented?

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