lumiera_documentation/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_CPU=25
LIMIT_VSZ=$((8 * 1014 * 1024))
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
Fix test breakage - some tests are notoriously flaky - increase resource limits for the testsuite to allow stronger stress tests - provide a "quick" variant of BufferProviderLoad_test with lowered requirements Furthermore, investigate test scaffolding in `DummyBuilderContext`, which was broken due to the clean-up in `DiagnosticOutputSlot`. It seems that only some placeholder instances are required here, so that we might be successful with just instantiating the `UnimplementedConnection` __TODO__: need to supply slightly more implementation into the latter, so that we're able at least to ''create'' such a connection stub. 2026-05-31 23:48:26 +02:00			`LIMIT_CPU=25`
Testsuite: increase virtual memory limit Set ulimit -v setting to 8 GiB (setting is given in kbyte) Otherwise it is not possible to start 100 Threads. This is surprising, because the actual memory usage of the tests in question are minuscule and also TOP does not show any significant memory peak when running the test. 2023-10-04 22:42:37 +02:00			`LIMIT_VSZ=$((8 * 1014 * 1024))`