Skip to content
Snippets Groups Projects
Commit 5d753c1e authored by Nikolay Shirokovskiy's avatar Nikolay Shirokovskiy Committed by Vladimir Davydov
Browse files

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 84cb1e04 ("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

(cherry picked from commit 703d11fe)
parent fbe2d58e
No related branches found
No related tags found
Loading
#!/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()
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment