LUMIERA.clone/tests/test.conf

LOGSUPPRESS='^\(\*\*[0-9]*\*\* \)\?[0-9]\{10,\}[:!] \(TRACE\|INFO\|NOTICE\|WARNING\|ERR\|TODO\|PLANNED\|FIXME\|DEPRECATED\|UNIMPLEMENTED\|RESOURCE_ANNOUNCE\|RESOURCE_ENTER\|RESOURCE_STATE\|RESOURCE_LEAVE\):'

LIMIT_VG_CPU=55
LIMIT_VG_TIME=60
update for nobug-201002.1 2010-02-03 10:38:12 +01:00			`LOGSUPPRESS='^\(\\[0-9]\\* \)\?[0-9]\{10,\}[:!] \(TRACE\\|INFO\\|NOTICE\\|WARNING\\|ERR\\|TODO\\|PLANNED\\|FIXME\\|DEPRECATED\\|UNIMPLEMENTED\\|RESOURCE_ANNOUNCE\\|RESOURCE_ENTER\\|RESOURCE_STATE\\|RESOURCE_LEAVE\):'`
Increase valgrind time limits for tests and fix test.sh glitch On my slow laptop some tests fail because of timeouts under valgrind, going to 55/60 seconds should be sane. Fixing an undiscovered bug ignoring timeout configs in test.sh. 2010-07-16 21:47:08 +02:00
			`LIMIT_VG_CPU=55`
			`LIMIT_VG_TIME=60`