test: fix fix-mips64-spare-side-exit-patching

The aforementioned test is flaky when run under Tarantool due to not enough room for all traces. The flushing of all traces at the start and collecting them solves the issue. The same issue may occur for the <gh-6098-fix-side-exit-patching-on-arm64.test.lua>, so it is adjusted as well. Reviewed-by: Sergey Bronnikov <[email protected]> Signed-off-by: Sergey Kaplun <[email protected]>
tarantool · Mar 3, 2025 · 42cd8d6 · 42cd8d6
1 parent dd0db0c
commit 42cd8d6
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 0 deletions.
diff --git a/test/tarantool-tests/fix-mips64-spare-side-exit-patching.test.lua b/test/tarantool-tests/fix-mips64-spare-side-exit-patching.test.lua
@@ -15,6 +15,11 @@ local MAXTRACE = 2000;
 
 test:plan(1)
 
+-- Flush all possible traces and collect them to be sure that
+-- we have enough space.
+jit.flush()
+collectgarbage()
+
 local function find_last_trace()
   local candidate = misc.getmetrics().jit_trace_num
   for traceno = candidate, MAXTRACE do

diff --git a/test/tarantool-tests/gh-6098-fix-side-exit-patching-on-arm64.test.lua b/test/tarantool-tests/gh-6098-fix-side-exit-patching-on-arm64.test.lua
@@ -9,6 +9,11 @@ local frontend = require('utils').frontend
 
 test:plan(1)
 
+-- Flush all possible traces and collect them to be sure that
+-- we have enough space.
+jit.flush()
+collectgarbage()
+
 -- The function to be tested for side exit patching:
 -- * At the beginning of the test case, the <if> branch is
 --   recorded as a root trace.