On 5 Feb 2007, at 18:20, Eric Wilhelm wrote:
Unfortunately that disqualifies a whole category of I/O bound tests
that would otherwise benefit the most.
Well, it disqualifies them from running on the same box/chroot/
whatever.
Consider a scheme that uses FAM+rsync to keep another box in lock-step
with your working copy and prepending ssh to the subprocess -- we
still
just read the output and exit code from the child. Distributed tests
will need the same slave/master scheme support as in the concurrent
single-box situation.
Hmm. That ups the ante a bit. I guess there are already frameworks
available that'd help with managing that kind of distributed setup?
The most similar thing I have any experience of is distcc[1].
As a matter of interest I wonder if anyone's worked out whether
Perl's build process plays nicely with distcc? A nice test case for
distributed tests might be to start with a working distributed build
process and then find a way of making the post-build tests
distributed too.
[1] http://distcc.samba.org/
--
Andy Armstrong, hexten.net
