[Webkit-unassigned] [Bug 58625] new-run-webkit-tests: runs tests in a different order than ORWT

[bugzilla-daemon at webkit.org]

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


Dirk Pranke <dpranke at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |WONTFIX
         AssignedTo|dpranke at chromium.org        |webkit-unassigned at lists.web
                   |                            |kit.org




--- Comment #10 from Dirk Pranke <dpranke at chromium.org>  2011-06-24 14:47:25 PST ---
(In reply to comment #9)
> (In reply to comment #8)
> > I think it makes sense to special-case the single-process case to run the http tests last. If you have >2 shards, not doing them first causes the tests to take longer to run.
> 
> We could do that, but I don't expect people to run the single-process case very often, so I'm not sure if it's worth it. That said, it's probably a one-line change ...

Okay, given the changes I've been making so that we can run more than one http test concurrently, this isn't really a one-line change any more, if you want to run the non-http tests without holding the http lock. See the comments I've made in the patch on bug 63112, and I'm unconvinced that it's worth it.

For now, I'm closing this as WONTFIX (and clearing the ownership). If anyone really thinks this needs to be fixed, please feel free to reopen.

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