CI: Use larger timeout multiplier for ASan tests

Running under ASan introduces a good amount of overhead. Using the Meson
test wrapper rather than invoking a Ninja target lets us set a timeout
multiplier, which we smash up pretty high to account for this overhead
and prevent some of the larger tests from hitting timeout.

Signed-off-by: Daniel Stone <daniels@collabora.com>
dev
Daniel Stone 3 years ago
parent 5c303cc116
commit e649c12316
  1. 4
      .gitlab-ci/virtme-scripts/run-weston-tests.sh

@ -15,13 +15,15 @@ export LIBSEAT_BACKEND=seatd
# virtme starts with HOME=/tmp/roothome, but as we installed meson on user root, # virtme starts with HOME=/tmp/roothome, but as we installed meson on user root,
# meson can not find its modules. So we change the HOME env var to fix that. # meson can not find its modules. So we change the HOME env var to fix that.
export HOME=/root export HOME=/root
export PATH=$HOME/.local/bin:$PATH
# start seatd and wait for its socket to be available before running the test # start seatd and wait for its socket to be available before running the test
/usr/local/bin/seatd & /usr/local/bin/seatd &
while ! [ -e /run/seatd.sock ]; do sleep 0.1; done while ! [ -e /run/seatd.sock ]; do sleep 0.1; done
# run the tests and save the exit status # run the tests and save the exit status
ASAN_OPTIONS=detect_leaks=0,atexit=1 ninja test # we give ourselves a very generous timeout multiplier due to ASan overhead
ASAN_OPTIONS=detect_leaks=0,atexit=1 meson test --timeout-multiplier 4
TEST_RES=$? TEST_RES=$?
# create a file to keep the result of this script: # create a file to keep the result of this script:

Loading…
Cancel
Save