contest: vm: scan with kmemleak twice

During 6.14 merge window we noticed that IOAM6 tests would cause
a leak and it was only detected after the next test. Manual testing
confirms the same behavior. Just to me sure scan for leaks twice.

Signed-off-by: Jakub Kicinski <[email protected]>

Author: kuba-moo

contest/remote/lib/vm.py

@@ -395,6 +395,10 @@ def check_health(self):
         if self.has_kmemleak:
             self.cmd("echo scan > /sys/kernel/debug/kmemleak && cat /sys/kernel/debug/kmemleak")
             self.drain_to_prompt()
+            # Do it twice, kmemleak likes to hide the leak on the first attempt
+            self.cmd("echo scan > /sys/kernel/debug/kmemleak && cat /sys/kernel/debug/kmemleak")
+            self.drain_to_prompt()
+
 
     def capture_gcov(self, dest):
         if not self.has_gcov: