tests: ignore valgrind warnings for unhandled syscalls in libnm,service-provider tests
Otherwise, we get test failures with valgrind on fedora:rawhide (valgrind-3.15.0-18.fc33.x86_64.rpm, gcc-10.0.1-0.8.fc33.x86_64, glib2-devel-2.63.5-3.fc33.x86_64): >>>> PRINT VALGRIND LOGS (valgrind test) (start) + find -name '*.valgrind-log' -print0 + xargs -0 grep -H '^' ./src/devices/wwan/tests/test-service-providers.valgrind-log:--95634-- WARNING: unhandled amd64-linux syscall: 315 ./src/devices/wwan/tests/test-service-providers.valgrind-log:--95634-- You may be able to write your own handler. ./src/devices/wwan/tests/test-service-providers.valgrind-log:--95634-- Read the file README_MISSING_SYSCALL_OR_IOCTL. ./src/devices/wwan/tests/test-service-providers.valgrind-log:--95634-- Nevertheless we consider this a bug. Please report ./src/devices/wwan/tests/test-service-providers.valgrind-log:--95634-- it at http://valgrind.org/support/bug_reports.html. ./libnm/tests/test-remote-settings-client.valgrind-log:--95245-- WARNING: unhandled amd64-linux syscall: 315 ./libnm/tests/test-remote-settings-client.valgrind-log:--95245-- You may be able to write your own handler. ./libnm/tests/test-remote-settings-client.valgrind-log:--95245-- Read the file README_MISSING_SYSCALL_OR_IOCTL. ./libnm/tests/test-remote-settings-client.valgrind-log:--95245-- Nevertheless we consider this a bug. Please report ./libnm/tests/test-remote-settings-client.valgrind-log:--95245-- it at http://valgrind.org/support/bug_reports.html. ./libnm/tests/test-secret-agent.valgrind-log:--95280-- WARNING: unhandled amd64-linux syscall: 315 ./libnm/tests/test-secret-agent.valgrind-log:--95280-- You may be able to write your own handler. ./libnm/tests/test-secret-agent.valgrind-log:--95280-- Read the file README_MISSING_SYSCALL_OR_IOCTL. ./libnm/tests/test-secret-agent.valgrind-log:--95280-- Nevertheless we consider this a bug. Please report ./libnm/tests/test-secret-agent.valgrind-log:--95280-- it at http://valgrind.org/support/bug_reports.html. ./libnm/tests/test-nm-client.valgrind-log:--95208-- WARNING: unhandled amd64-linux syscall: 315 ./libnm/tests/test-nm-client.valgrind-log:--95208-- You may be able to write your own handler. ./libnm/tests/test-nm-client.valgrind-log:--95208-- Read the file README_MISSING_SYSCALL_OR_IOCTL. ./libnm/tests/test-nm-client.valgrind-log:--95208-- Nevertheless we consider this a bug. Please report ./libnm/tests/test-nm-client.valgrind-log:--95208-- it at http://valgrind.org/support/bug_reports.html. + echo '>>>> PRINT VALGRIND LOGS (valgrind test) (done)' >>>> PRINT VALGRIND LOGS (valgrind test) (done)
This commit is contained in:
@@ -295,12 +295,18 @@ fi
|
|||||||
if [ $HAS_ERRORS -eq 0 ]; then
|
if [ $HAS_ERRORS -eq 0 ]; then
|
||||||
# valgrind doesn't support setns syscall and spams the logfile.
|
# valgrind doesn't support setns syscall and spams the logfile.
|
||||||
# hack around it...
|
# hack around it...
|
||||||
if [ "$TEST_NAME" = 'test-link-linux' -o \
|
case "$TEST_NAME" in
|
||||||
"$TEST_NAME" = 'test-acd' ]; then
|
'test-link-linux' | \
|
||||||
if [ -z "$(sed -e '/^--[0-9]\+-- WARNING: unhandled .* syscall: /,/^--[0-9]\+-- it at http.*\.$/d' "$LOGFILE")" ]; then
|
'test-acd' | \
|
||||||
HAS_ERRORS=1
|
'test-service-providers' | \
|
||||||
fi
|
'test-remote-settings-client' | \
|
||||||
fi
|
'test-secret-agent' | \
|
||||||
|
'test-nm-client' )
|
||||||
|
if [ -z "$(sed -e '/^--[0-9]\+-- WARNING: unhandled .* syscall: /,/^--[0-9]\+-- it at http.*\.$/d' "$LOGFILE")" ]; then
|
||||||
|
HAS_ERRORS=1
|
||||||
|
fi
|
||||||
|
;;
|
||||||
|
esac
|
||||||
fi
|
fi
|
||||||
|
|
||||||
if [ $HAS_ERRORS -eq 0 ]; then
|
if [ $HAS_ERRORS -eq 0 ]; then
|
||||||
|
Reference in New Issue
Block a user