Adds a memory leak check after running a unit test

[rjd15372]

This commit adds check after each test function execution of a unit test, that checks if there is still memory allocated.

This check prevents situations where tests, which do these kind of checks, fail due to memory leaks caused by previous tests.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.99%. Comparing base (4966357) to head (b02f1bc).
Report is 4 commits behind head on unstable.

Additional details and impacted files

@@             Coverage Diff              @@
##           unstable    #1798      +/-   ##
============================================
+ Coverage     70.97%   70.99%   +0.02%     
============================================
  Files           123      123              
  Lines         65645    65648       +3     
============================================
+ Hits          46590    46607      +17     
+ Misses        19055    19041      -14     

see 30 files with indirect coverage changes

[madolson]

Seems to be a lot of memory leaks though :/

[zuiderkwast]

Seems to be a lot of memory leaks though :/

Hm... Are the test cases not independent? If not, then maybe we should just detect leaks between each suite...?

[madolson]

Yeah, it looks like the listpack tests are cumulative, which is interesting. We should probably make each one self contained, so we can run it without the others.

[zuiderkwast]

Yeah, it looks like the listpack tests are cumulative, which is interesting. We should probably make each one self contained, so we can run it without the others.

There's currently no way to run a single test case though. It'd be more work to refactor these tests so I suggest we just check mem leaks per suite. It's much easier.

[madolson]

There's currently no way to run a single test case though. It'd be more work to refactor these tests so I suggest we just check mem leaks per suite. It's much easier.

I'm okay with that for now.