From 3e616c306d6d80d278efd0b9dd3a2d2d500245d7 Mon Sep 17 00:00:00 2001 From: Thomas Haller Date: Fri, 21 Feb 2020 11:16:13 +0100 Subject: 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) --- tools/run-nm-test.sh | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) (limited to 'tools') diff --git a/tools/run-nm-test.sh b/tools/run-nm-test.sh index 140236dcb3..21f0d7c154 100755 --- a/tools/run-nm-test.sh +++ b/tools/run-nm-test.sh @@ -295,12 +295,18 @@ fi if [ $HAS_ERRORS -eq 0 ]; then # valgrind doesn't support setns syscall and spams the logfile. # hack around it... - if [ "$TEST_NAME" = 'test-link-linux' -o \ - "$TEST_NAME" = 'test-acd' ]; then - if [ -z "$(sed -e '/^--[0-9]\+-- WARNING: unhandled .* syscall: /,/^--[0-9]\+-- it at http.*\.$/d' "$LOGFILE")" ]; then - HAS_ERRORS=1 - fi - fi + case "$TEST_NAME" in + 'test-link-linux' | \ + 'test-acd' | \ + 'test-service-providers' | \ + 'test-remote-settings-client' | \ + '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 if [ $HAS_ERRORS -eq 0 ]; then -- cgit v1.2.1