#2444 introduced a bug, and will be disabled until fixed.
We spent time in #2503 trying to debug and fix the issue, and after inspecting a trace generated by the failing test, we found that there were hundreds upon hundreds of syscalls walking the filesystem directories when telemetry was started up as part of DetectLibDl. A few milliseconds one time isn't a massive deal, but it added up quickly, to the point where tests were timing out after 70 seconds.