3 commits

Author	SHA1	Message	Date
Davi Arnaut	2b5180b98b	Test is very resource intensive under debug and valgrind runs. ... Under a debug run, the trace file grows to a few gigabytes. Under valgrind, takes more then 20 minutes due to the high number of insert statements.	2009-06-08 19:18:31 -03:00
Davi Arnaut	8209a09ef6	Test is very resource intensive under debug and valgrind runs. ... Under a debug run, the trace file grows to a few gigabytes. Under valgrind, takes more then 20 minutes due to the high number of insert statements.	2009-06-08 12:51:06 -03:00
Matthias Leich	177c0c2a3c	Fix for Bug#26890 main.multi_update times out ... The test itself is not faulty. The testcase timeout problem happens if this IMHO mid size resource (space in vardir, virtual memory, amount of disk I/O) consuming test meets a weak (excessive disk I/O caused by parallel applications or paging) testing box. The modifications: - Move the most time and disk I/O consuming subtest for Bug 1820 into its own script (multi_update2) This will reduce the likelihood that we exceed the testcase timeout. - Replace error numbers with error names - Minor improvements of the formatting -	2008-11-19 19:17:26 +01:00