From 703d11fe10eb8c1d2f688949808e6ddae498df1c Mon Sep 17 00:00:00 2001
From: Nikolay Shirokovskiy <nshirokovskiy@tarantool.org>
Date: Mon, 23 Oct 2023 10:54:31 +0300
Subject: [PATCH] test: increase expected selectG execution time for debug ASAN
build
The test is quite a flacky in debug ASAN CI workflow. The issue is test
check upper boundary of it's execution time. I run many instances of
this test on in parallel and got average time of 40s for memtex and 70s
for vinyl.
The time quota is already changed by the commit 84cb1e049272 ("sql:
increase time quota for selectG test on vinyl") for laptops with HDD.
I did not check execution time for HDD though. I guess the bottleneck
for debug ASAN is CPU.
Follow-up #7327
NO_CHANGELOG=internal
NO_DOC=internal
---
test/sql-tap/selectG.test.lua | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/test/sql-tap/selectG.test.lua b/test/sql-tap/selectG.test.lua
index 0690b4c863..63777d7b0d 100755
--- a/test/sql-tap/selectG.test.lua
+++ b/test/sql-tap/selectG.test.lua
@@ -1,5 +1,6 @@
#!/usr/bin/env tarantool
local test = require("sqltester")
+local tarantool = require('tarantool')
test:plan(1)
--!./tcltestrunner.lua
@@ -27,9 +28,14 @@ test:plan(1)
-- the insert run for over a minute.
--
local engine = test:engine()
-local time_quota =
- engine == 'memtx' and 25 or (
- engine == 'vinyl' and 50 or 0) -- seconds
+local time_quota
+if tarantool.build.asan then
+ time_quota = engine == 'memtx' and 80 or (
+ engine == 'vinyl' and 140 or 0) -- seconds
+else
+ time_quota = engine == 'memtx' and 25 or (
+ engine == 'vinyl' and 50 or 0) -- seconds
+end
test:do_test(
100,
function()
--
GitLab