Re: [Valgrind-testresults] 2025-11-17 03:00:09 UTC nightly build (gcc110, \S, ppc64)

[Paul F. <pj...@wa...>]

> On 17 Nov 2025, at 05:35, Philippe Waroquiers via valgrind-testresults <val...@li...> wrote:
> 
> valgrind revision: valgrind-3.27.0.GIT-fafb6efd4b-20251116
> C compiler:        gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
> GDB:               GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7
> Assembler:         GNU assembler version 2.27-44.base.el7_9.1
> C library:         GNU C Library (GNU libc) stable release version 2.17
> uname -mrs:        Linux 3.10.0-1160.105.1.el7.ppc64 ppc64
> Vendor version:    CentOS Linux 7 (AltArch)
> 
> Nightly build on gcc110 ( \S, ppc64 )
> Started at 2025-11-17 03:00:09 UTC
> Ended   at 2025-11-17 04:35:31 UTC
> Results differ from 24 hours ago
> 
>   Checking out Valgrind source tree  ... done
>   Configuring valgrind               ... done
>   Building valgrind                  ... done
>   Running regression tests           ... failed
> 
> Regression test results follow
> 
> == 774 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
> memcheck/tests/leak_cpp_interior         (stderr)
> none/tests/fdleak_ipv4                   (stderr)


Tonight I’ll see if I can reproduce and understand the fdleak_ipv4 failure

A+
Paul