libglvnd/.gitlab-ci/run_meson.sh

#!/bin/bash

set -e
set -o xtrace

# Running a unity build (sometimes called a jumbo build) is both a useful thing
# to test and reduces compile time.
#
# Enable all auto-features to ensure that we're properly testing all optional
# dependencies.
meson build -Dwerror=true --unity=on --auto-features=enabled $CONFIGURE_OPTIONS
ninja -C build

xvfb-run --auto-servernum ninja -C build test
gitlab-ci: Add meson build support 2019-11-14 23:26:24 +01:00			`#!/bin/bash`

			`set -e`
			`set -o xtrace`

			`# Running a unity build (sometimes called a jumbo build) is both a useful thing`
			`# to test and reduces compile time.`
			`#`
gitlab-ci: Build with -Werror The next commit will remove -Werror from the default autotools and meson builds, but we would like to continue treating warnings as errors in CI. 2020-06-25 19:55:29 +02:00			`# Enable all auto-features to ensure that we're properly testing all optional`
gitlab-ci: Add meson build support 2019-11-14 23:26:24 +01:00			`# dependencies.`
gitlab-ci: Build with -Werror The next commit will remove -Werror from the default autotools and meson builds, but we would like to continue treating warnings as errors in CI. 2020-06-25 19:55:29 +02:00			`meson build -Dwerror=true --unity=on --auto-features=enabled $CONFIGURE_OPTIONS`
gitlab-ci: Add meson build support 2019-11-14 23:26:24 +01:00			`ninja -C build`

gitlab-ci: Use xvfb-run Change the CI scripts to use xvfb-run instead of running Xvfb directly. That avoids a potential race condition, where a test could fail because Xvfb hasn't started listening for connections yet. xvfb-run will wait for Xvfb to be ready before it runs any other programs. That also simplifies error handling, because the CI scripts can just use "set -e" instead of having to store the exit code, kill Xvfb, and then check for an error. 2019-12-09 19:34:12 +01:00			`xvfb-run --auto-servernum ninja -C build test`