testbench: cleanup, including fix of false positives
some environments have faulty components; also some tests failed simply because
their runtime *is* far longer than supported by default. Also re-instantiated
some "lost" tests and done some general cleanup.
while we solved valgrind false positives during shutdown in
2700badfda76c701fa9169c31c9ec4f7993dc0b8, we continue to see
related messages for thread-local-storages. Rather than suppressing
these as well we now refactored the code so that it does not use
detached threads.
This shall improve robustness. In case it does not, we have enhanced
debug messages under CI runs, so potentially still-existing problem
areas should be easier to diagnose.
see also https://github.com/rsyslog/rsyslog/issues/2902
finally I give up and honestly think this is a problem in pthreads and
not in rsyslog code. See issue below and pervious commit for more
information.
Unfortunately, this will also mask off cases where we do not properly
call pthread_join() albeit it is needed. Neverthless, this bug is
causing so much CI grief that it is definitely worth it.
closes https://github.com/rsyslog/rsyslog/issues/2902
Valgrind log in --leck-check=all mode is sometimes hard to read as we
intensionally do not unload modules during testing to get hold of
debug symbol resolution. This creates a memleak. We have now added
valgrind suppressions to not show these.
