<p dir="auto">For tests that must (for some reason) leak an operation or resource deno test allows us to <a href="https://deno.land/manual/testing#resource-and-async-op-sanitizers" rel="nofollow">opt out of Op and Resource sanitizing for a single test</a>. Unfortunately, the resources purposefully leaked by a "leaky" test end up associated with other tests, causing hard to diagnose errors.</p>
<p dir="auto">I've created a minimal reproduction of the issue in <a href="https://github.com/baetheus/deno_leaky_async_bug">this repository</a>.</p>
<p dir="auto">Thanks for all the hard work you guys are doing!</p>
<p dir="auto">It would be nice to be able to see the async objects that are leaking and their allocation stack. I think this would be useful as a command line switch to enable it while debugging. For my complex application, one part of the system seems to be affecting a different part. Their individual unit tests execute just fine. When running the entire test on the system, I'm getting random failures.</p>
<p dir="auto">Right now I'm hunting for the leaking ops and adding more test coverage, but it would be nice to have some insight here.</p>