With Meson 0.63.0, detailed output of TAP tests is not logged, and the
test deadlocks if the stderr pipe fills up. I'm hoping this will be fixed
before 0.63.1, but in the meantime we can work around it by falling back
to the 'exitcode' protocol: this means we lose machine-readable detailed
test results, but at least our tests pass.
See https://github.com/mesonbuild/meson/issues/10577 and
https://github.com/mesonbuild/meson/issues/10563 for details of the
Meson regression.
Signed-off-by: Simon McVittie <smcv@collabora.com>
installed_tests = []
+if meson.version().version_compare('>=0.63')
+ # Work around https://github.com/mesonbuild/meson/issues/10577
+ test_protocol = 'exitcode'
+else
+ test_protocol = 'tap'
+endif
+
###############################################################################
# Dbus testutils
test_exe,
args: ['--tap'],
env: test_env,
- protocol: 'tap',
+ protocol: test_protocol,
suite: suites,
timeout: timeout,
)
test_exe,
],
env: test_env,
- protocol: 'tap',
+ protocol: test_protocol,
suite: suites,
timeout: timeout,
)
test('run-test',
find_program('run-test.sh'),
env: test_env,
- protocol: 'tap',
+ protocol: test_protocol,
suite: 'name-test',
)
test('run-test-systemserver',
find_program('run-test-systemserver.sh'),
env: test_env,
- protocol: 'tap',
+ protocol: test_protocol,
suite: 'name-test',
)
endif