# from Ovid
# on Monday 19 November 2007 03:04:
>That avoids the overhead of reloading perl and the modules multiple
> times. However, each .yml file defines its own test count and I
> don't want 'no_plan'.
So, you write a custom 'exec' program which starts a daemon (the first
time (e.g. checks a lockfile)) and passes it the name of the test file
(on a socket/fifo.) The daemon has preloaded all of the modules, then
forks-off a new process to run each test. The harness sees it as
multiple tests, so the plans are fine.
Now you can get it down to 1.5min if you have a second CPU.
Some sort of preload support in TAP::Harness would be nice.
Also note, with SGI::FAM, a persistent daemon could conceivably have
already loaded the new code before you can reach for the hotkey to
start the tests.
--Eric
--
To a database person, every nail looks like a thumb.
--Jamie Zawinski
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
