b1f6d53bc4
The defaults for test timeouts in meson is 30 seconds. That is not long enough when running $ NMTST_USE_VALGRIND=1 ninja -C build test Note that meson supports --timeout-multiplier, and automatically increases the timeout when running under valgrind. However, meson does not understand that we are running tests under valgrind via NMTST_USE_VALGRIND=1 environment variable. Timeouts are really not expected to be reached and are a mean of last resort. Hence, increasing the timeout to a large value is likely to have no effect or to fix test failures where the timeout was too rigid. It's unlikely that the test indeed hangs and the increase of timeout causes a unnecessary increase of waittime before aborting.
53 lines
1.2 KiB
Meson
53 lines
1.2 KiB
Meson
# test-cert.p12 created with:
|
|
#
|
|
# openssl pkcs12 -export \
|
|
# -in test_key_and_cert.pem \
|
|
# -inkey test_key_and_cert.pem \
|
|
# -certfile test_ca_cert.pem \
|
|
# -name "test-pkcs12" \
|
|
# -out test-cert.p12
|
|
|
|
enum_types = 'nm-core-tests-enum-types'
|
|
|
|
enum = gnome.mkenums(
|
|
enum_types,
|
|
sources: 'test-general-enums.h',
|
|
identifier_prefix: nm_id_prefix,
|
|
c_template: enum_types + '.c.template',
|
|
h_template: enum_types + '.h.template',
|
|
)
|
|
|
|
test_units = [
|
|
'test-compare',
|
|
'test-crypto',
|
|
'test-general',
|
|
'test-keyfile',
|
|
'test-secrets',
|
|
'test-setting',
|
|
'test-settings-defaults',
|
|
]
|
|
|
|
test_cert_dir = join_paths(meson.current_source_dir(), 'certs')
|
|
|
|
foreach test_unit: test_units
|
|
exe = executable(
|
|
'libnm-core-' + test_unit,
|
|
[test_unit + '.c'] + enum,
|
|
dependencies: [
|
|
nm_core_dep,
|
|
libnm_systemd_shared_no_logging_dep,
|
|
],
|
|
c_args: [
|
|
'-DNETWORKMANAGER_COMPILATION_TEST',
|
|
'-DNETWORKMANAGER_COMPILATION=NM_NETWORKMANAGER_COMPILATION_LIBNM_CORE',
|
|
],
|
|
link_with: libnm_core,
|
|
)
|
|
test(
|
|
'libnm-core/' + test_unit,
|
|
test_script,
|
|
args: test_args + [exe.full_path()],
|
|
timeout: default_test_timeout,
|
|
)
|
|
endforeach
|