Created attachment 767454 [details] build.log.xz [...] for bin in test-lib; do \ if ! /bin/sh ../../libtool execute /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \ done valgrind: m_syswrap/syswrap-main.c:549 (getSyscallArgsFromGuestState): Assertion 'gst->guest_syscall_fla g == SC_FLAG' failed. host stacktrace: ==169670== at 0x580559E8: ??? (in /usr/libexec/valgrind/memcheck-ppc64be-linux) ==169670== by 0x58055B87: ??? (in /usr/libexec/valgrind/memcheck-ppc64be-linux) ==169670== by 0x58055D03: ??? (in /usr/libexec/valgrind/memcheck-ppc64be-linux) ==169670== by 0x580CEBFF: ??? (in /usr/libexec/valgrind/memcheck-ppc64be-linux) ==169670== by 0x580C8A67: ??? (in /usr/libexec/valgrind/memcheck-ppc64be-linux) ==169670== by 0x580CB8FB: ??? (in /usr/libexec/valgrind/memcheck-ppc64be-linux) ==169670== by 0x5812378F: ??? (in /usr/libexec/valgrind/memcheck-ppc64be-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 169670) ==169670== at 0x492F8B4: getrandom (getrandom.c:29) ==169670== by 0x1D2E37: random_read (in /var/tmp/portage/net-mail/dovecot-2.3.18/work/dovecot-2.3.18/ src/lib/test-lib) ==169670== by 0x1D30CF: random_fill (in /var/tmp/portage/net-mail/dovecot-2.3.18/work/dovecot-2.3.18/ src/lib/test-lib) ==169670== by 0x1D3237: random_init (in /var/tmp/portage/net-mail/dovecot-2.3.18/work/dovecot-2.3.18/ src/lib/test-lib) ==169670== by 0x1B9843: lib_init (in /var/tmp/portage/net-mail/dovecot-2.3.18/work/dovecot-2.3.18/src /lib/test-lib) ==169670== by 0x181353: test_run_named_with_fatals (in /var/tmp/portage/net-mail/dovecot-2.3.18/work/dovecot-2.3.18/src/lib/test-lib) ==169670== by 0x13680B: main (in /var/tmp/portage/net-mail/dovecot-2.3.18/work/dovecot-2.3.18/src/lib/test-lib) client stack range: [0x1FFEFFA000 0x1FFF000FFF] client SP: 0x1FFEFFC660 valgrind stack range: [0x1003127000 0x1003226FFF] top usage: 20832 of 1048576
Created attachment 767455 [details] emerge --info
Can you report this upstream if git master fails?
(In reply to Sam James from comment #2) > Can you report this upstream if git master fails? Current git master does not run these valgrind tests. git 2.3.18 shows the same output as here.
Created attachment 768169 [details] build.log.xz (ppc64, 2.3.14.1-r2) 2.3.14.1-r2 does not show these valgrind failures. According to the build.log it does not pick up valgrind at all (despite dev-util/valgrind-3.18.1 being installed).
This looks like a real Valgrind problem we should report to them, but see bug 340791 & bug 807178 for no longer automagically running Valgrind tests in Gentoo for dovecot. Could you report this upstream to Valgrind?
(In reply to Sam James from comment #5) > This looks like a real Valgrind problem we should report to them, but see > bug 340791 & bug 807178 for no longer automagically running Valgrind tests > in Gentoo for dovecot. > > Could you report this upstream to Valgrind? (if you can reproduce it by running valgrind on something simple, like 'valgrind bash').
meh, I think this might be https://bugs.kde.org/show_bug.cgi?id=398883.
I think this is fixed in 3.0.21 by https://sourceware.org/git/?p=valgrind.git;a=commit;h=b4ec6a6ff767098714ffa8c4e3e3081d98fd2d66.