nixo
/
gri3-wm
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
gri3-wm/travis/run-tests.sh

33 lines
825 B
Bash
Raw Normal View History

travis: check spelling of binaries and manpages, use docker We now build a docker base container based on debian sid (where the very latest packages are available). That base container is updated once a month, or whenever travis-build.Dockerfile or debian/control change, but re-used for subsequent travis runs. While the initial build might take up to 15 minutes, subsequent builds typically run in a minute or two. All the different steps that we run on travis are now factored into separate scripts in the travis/ directory. Switching to docker should also help with issue #2174.
2016-02-01 09:42:55 +01:00
#!/bin/sh
travis: build debian packages and documentation The resulting packages are pushed to Debian repositories hosted on bintray.com. This is the first step to move away from our custom buildbot setup (see https://i3wm.org/docs/buildbot.html for details on that) towards infrastructure which is more standard (travis) and in the open.
2016-03-27 21:11:30 +02:00
set -e
set -x
Update travis for autotools
2016-10-16 18:03:09 +02:00
cd build
travis: work around asan broken-ness with libc ≥ 2.24 fixes #2437
2016-09-05 08:42:34 +02:00
# TODO: remove this workaround once https://bugs.debian.org/836723 is fixed
# Found at https://llvm.org/bugs/show_bug.cgi?id=27310#c8:
travis: only enable asan workaround for clang (breaks gcc) fixes #2437
2016-09-05 08:55:26 +02:00
if [ "$CC" = "clang" ]
then
cat >fixasan.c <<EOT
travis: work around asan broken-ness with libc ≥ 2.24 fixes #2437
2016-09-05 08:42:34 +02:00
void __isoc99_printf() {}
void __isoc99_sprintf() {}
void __isoc99_snprintf() {}
void __isoc99_fprintf() {}
void __isoc99_vprintf() {}
void __isoc99_vsprintf() {}
void __isoc99_vsnprintf() {}
void __isoc99_vfprintf() {}
void __cxa_throw() {} // NEW
EOT
travis: only enable asan workaround for clang (breaks gcc) fixes #2437
2016-09-05 08:55:26 +02:00
gcc fixasan.c -o fixasan.so -fPIC -shared -nostdlib
export LD_PRELOAD=$PWD/fixasan.so
fi
travis: work around asan broken-ness with libc ≥ 2.24 fixes #2437
2016-09-05 08:42:34 +02:00
travis: check spelling of binaries and manpages, use docker We now build a docker base container based on debian sid (where the very latest packages are available). That base container is updated once a month, or whenever travis-build.Dockerfile or debian/control change, but re-used for subsequent travis runs. While the initial build might take up to 15 minutes, subsequent builds typically run in a minute or two. All the different steps that we run on travis are now factored into separate scripts in the travis/ directory. Switching to docker should also help with issue #2174.
2016-02-01 09:42:55 +01:00
# Try running the tests in parallel so that the common case (tests pass) is
# quick, but fall back to running them in sequence to make debugging easier.
tests: run under Xvfb by default (if available) (#2951) This shaves off two seconds of wall-clock time (10s → 8s).
2017-10-13 09:18:49 +02:00
if ! make check
travis: check spelling of binaries and manpages, use docker We now build a docker base container based on debian sid (where the very latest packages are available). That base container is updated once a month, or whenever travis-build.Dockerfile or debian/control change, but re-used for subsequent travis runs. While the initial build might take up to 15 minutes, subsequent builds typically run in a minute or two. All the different steps that we run on travis are now factored into separate scripts in the travis/ directory. Switching to docker should also help with issue #2174.
2016-02-01 09:42:55 +01:00
then
tests: run under Xvfb by default (if available) (#2951) This shaves off two seconds of wall-clock time (10s → 8s).
2017-10-13 09:18:49 +02:00
./testcases/complete-run.pl --parallel=1 || (cat latest/complete-run.log; false)
travis: check spelling of binaries and manpages, use docker We now build a docker base container based on debian sid (where the very latest packages are available). That base container is updated once a month, or whenever travis-build.Dockerfile or debian/control change, but re-used for subsequent travis runs. While the initial build might take up to 15 minutes, subsequent builds typically run in a minute or two. All the different steps that we run on travis are now factored into separate scripts in the travis/ directory. Switching to docker should also help with issue #2174.
2016-02-01 09:42:55 +01:00
fi