Tests are failing on several architectures
Tests are run several architectures ( http://autopkgtest.ubuntu.com/packages/libn/libnfs ) on Ubuntu's autopkgtest infrastructure and some of them are failing.
i386:
...
prog_statvfs.c:92:19: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 2 has type ‘__fsfilcnt64_t’ {aka ‘long long unsigned int’} [-Werror=format=]
printf("favail:%lu\n", svfs.f_favail);
~~^ ~~~~~~~~~~~~~
%llu
cc1: all warnings being treated as errors
make: Leaving directory '/tmp/autopkgtest.sSxhNM/build.JxP/src/tests'
...
arm64:
Running test_0212_fstat_valgrind_leak_check.sh
--------------
NFSv4 Basic valgrind leak check for nfs_fstat64().
test nfs_fstat64() (1) ... [OK]
test nfs_fstat64() (2) ... [OK]
test nfs_fstat64() (3) ... [OK]
test nfs_fstat64() (4) ... [OK]
test nfs_fstat64() (5) ... [OK]
test nfs_fstat64() (6) ... [FAILED]
make: Leaving directory '/tmp/autopkgtest.DSnpbn/build.PxF/src/tests'
make: *** [Makefile:1049: test] Error 1
ppc64el:
Running test_0202_stat_valgrind_leak_check.sh
--------------
NFSv4 Basic valgrind leak check for nfs_stat64()
test nfs_stat64() (1) ... [FAILED]
make: *** [Makefile:1049: test] Error 1
make: Leaving directory '/tmp/autopkgtest.6rAa7R/build.Qsi/src/tests'
The two latter may be Valgrind issues.
Please re-test with current master. These issues should be solved.
@sahlberg Thanks, those issues are resolved now. There are still some, which I already reported and you can also check the current autopkgtest results for all supported Ubuntu architectures at: https://bileto.ubuntu.com/excuses/3798/eoan.html
Packaging is kept at https://salsa.debian.org/debian/libnfs , where I still carry a few patches in debian/patches/ to keep tests passing.