LeakSan tests taking a very long time
Closed this issue · 2 comments
eigenraven commented
Just looking at recent actions logs, it looks like there's a lot of 30s sleeps between tests that for some reason only happen when testing with the Leak santitizer enabled.
csegarragonz commented
According to the docs the leak sanitizer should:
- Add no overhead.
- Be enabled by default with Address Sanitizer.
Do you know what could be happening then?
eigenraven commented
I have no idea, but if asan can already cover it we can probably just remove independent leaksan. The docs do say it is a much less tested/supported configuration.