All bots (except Qt) are now transitioned to using parallel testing by default.
As expected, this was a big win for all the bots. (Gtk 32-bit -- as a
randomly selected example -- went form 37min cycle times to 18min
cycle times.)
I expect there will be a few more flaky tests we'll need to
I should have said all platforms. run-webkit-tests will use
parallel testing on all platforms (except Qt), not just on the
buildbot machines.
-eric
On Mon, Dec 5, 2011 at 1:24 AM, Eric Seidel e...@webkit.org wrote:
All bots (except Qt) are now transitioned to using parallel testing by
On Dec 2, 2011, at 6:55 PM, Eric Seidel wrote:
The SnowLeopard bot went from a 1 hr 4 min (!?!) cycle time, to 38 min (still
!?!).
I suspect our Mac test bots could use a dose of RAM. Many of them only have
3GB, since when you're running tests one by one you don't really need much more.
Had to revert this for Mac in http://trac.webkit.org/changeset/102013 due
to 20+ tests timing out and nrwt existing early:
http://build.webkit.org/builders/SnowLeopard%20Intel%20Release%20%28Tests%29?numbuilds=100
- Ryosuke
On Mon, Dec 5, 2011 at 6:55 AM, Adam Roben aro...@apple.com wrote:
On
I looked at one example that didn't exit early:
http://build.webkit.org/builders/SnowLeopard%20Intel%20Release%20%28Tests%29/builds/35153/steps/layout-test/logs/stdio
In that case, the http tests were the long tail and took 6 minutes longer
than all the other tests. We don't split the http tests
I believe there are some tests (copy/paste) that it would be very hard to
fully shard due to how they work.
dave
On Mon, Dec 5, 2011 at 11:08 AM, Ojan Vafai o...@chromium.org wrote:
I looked at one example that didn't exit early:
Why is that? I don't know about other ports, but AFAIK, chromium writes to
a mock clipboard and the Apple mac port writes to a local OS clipboard
instance instead of the global one, specifically to avoid copy/paste tests
interacting. Even without running tests in parallel, it's probably a good
We never implemented the general way of marking subdirectories as
needing to run serially, but it would be easy to do if we needed to
[the 'http' dirs are still special-cased in the code].
There is code now (landed a few months ago) to control how many http
tests run in parallel separately from
On Mon, Dec 5, 2011 at 1:01 PM, Dirk Pranke dpra...@chromium.org wrote:
We never implemented the general way of marking subdirectories as
needing to run serially, but it would be easy to do if we needed to
[the 'http' dirs are still special-cased in the code].
Does it also special-case the
On Mon, Dec 5, 2011 at 1:53 PM, Eric U er...@google.com wrote:
On Mon, Dec 5, 2011 at 1:01 PM, Dirk Pranke dpra...@chromium.org wrote:
We never implemented the general way of marking subdirectories as
needing to run serially, but it would be easy to do if we needed to
[the 'http' dirs are
Some http tests make use of stateful php scritps with different tests
utlizing the same scripts in some cases. Does each 'worker' get a dedicated
http server instance or do they share the same http server?
On Mon, Dec 5, 2011 at 1:01 PM, Dirk Pranke dpra...@chromium.org wrote:
We never
if http server instance == apache child process, then no. We don't
do anything to particularly limit the number of apache children
running or bind them, but given that in the normal case there is only
ever one http test running at a time, you shouldn't see any issues
from contention.
(You would,
run-webkit-tests is moving to parallell testing by default (this weekend)
I just moved Mac this afternoon. The SnowLeopard bot went from a 1 hr
4 min (!?!) cycle time, to 38 min (still !?!).
http://build.webkit.org/builders/SnowLeopard%20Intel%20Debug%20%28Tests%29/builds/3317
On Fri, Dec 2, 2011 at 3:55 PM, Eric Seidel e...@webkit.org wrote:
run-webkit-tests is moving to parallell testing by default (this weekend)
I just moved Mac this afternoon. The SnowLeopard bot went from a 1 hr
4 min (!?!) cycle time, to 38 min (still !?!).
On Fri, Dec 2, 2011 at 6:44 PM, Dirk Pranke dpra...@chromium.org wrote:
some of those tests are taking 10 minutes or more to complete ...
there's clearly one or more bugs here keeping NRWT from timing out DRT
properly. Some are almost certainly in NRWT, but I wonder if there are
things in the
15 matches
Mail list logo
