On Thu, 2024-06-20 at 10:17 +0100, Alan Maguire wrote: [...] > I explored this further. Even adding a separate skeleton with tracing > prog to catch release is insufficient because the map free is deferred > and the test can have already run by the time the deferred map free is > called. Whatever mechanism we use to detect release would be subject to > the timing of that it seems. This seems like a recipe for a flaky test > and I'd rather not add sleeps etc so I've stuck with the current > approach which exercises the dtor codepaths but doesn't verify release. > Thanks! Makes sense, thank you for taking a look.
