On 2013/07/10 17:01:39, kpreid2 wrote:
On 2013/07/10 16:51:11, felix8a wrote:
> this still leaves failed windows alone. if a test fails, we drop the
webdriver
> instance so it stays around, and open a new one. is there something
else
> you need?
Oh, OK.
But doesn't that mean that the new webdriver will open a new browser?
I remember
we used to do that, and if someone accidentally breaks _all_ the tests
and runs
an unattended runtests, the memory usage of the resulting ~100 copies
of Firefox
can make a machine unusable.
if that's a problem I can put a max spawn limit there somewhere. I can
do that in a separate CL. our lack of firefox beta testing is hurting
more, beta is going to become release in less than a month.
https://codereview.appspot.com/10963044/
--
---
You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
