Some thoughts:

• Does the slowdown point to another issue with how we are running with Valgrind? test-valgrind-latest-server-auth-nosasl-openssl goes from ~10 minutes on some variants to exceeding 2 hours on the valgrind variant. Is a > 12x slowdown really normal?
• I wonder if the slowdown is caused by OpenSSL code being run on Valgrind. If so, we could change these test tasks to compile with OpenSSL support (so we can test sessions, and other tests that require crypto) but connect over plain sockets.
• Perhaps we can disable checks that ASAN already catches, and only leave the ones that ASAN does not catch (e.g. reads of uninitialized memory).