Kern Sibbald wrote:
> 3. I looked through the ctest section of the manual, but didn't find anything
> that could set a time limit on a particular test -- that would be very useful
> because particularly for the multidrive tests, Bacula will sometimes stall,
> and I would prefer that after 10 mins the test is killed and ctest moves on
> to the other tests ... it seems to me the easiest is to put a time limit in
> each of our scripts.
Adding this line to Index: DartConfiguration.tcl.in should cause ctest to kill
any tests after 10 minutes:
TimeOut: 600
Note that this doesn't appear to have any provisions for cleaning up after
jobs killed due to a timeout, so the scripts should probably be prepared to
handle an ungracefully killed predecessor.
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
