Re: [Valgrind-users] Valgrind-3.24.0.RC1 is available for testing

[Carl L. <ce...@li...>]

Mark:

PowerPC testing on Power 8, I am seeing 4 additional stderr failures 
versus Valgrind 3.23.0.RC2

  == 749 tests, 7 stderr failures, 0 stdout failures, 13 stderrB 
failures, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
gdbserver_tests/mcblocklistsearch (stderrB)
gdbserver_tests/mcbreak (stderrB)
gdbserver_tests/mcclean_after_fork (stderrB)
gdbserver_tests/mcinfcallWSRU (stderrB)
gdbserver_tests/mcleak (stderrB)
gdbserver_tests/mcmain_pic (stderrB)
gdbserver_tests/mcvabits (stderrB)
gdbserver_tests/mssnapshot (stderrB)
gdbserver_tests/nlgone_abrt (stderrB)
gdbserver_tests/nlgone_exit (stderrB)
gdbserver_tests/nlgone_return (stderrB)
gdbserver_tests/nlpasssigalrm (stderrB)
memcheck/tests/leak_cpp_interior (stderr)
memcheck/tests/linux/rfcomm (stderr)
memcheck/tests/linux/sys-execveat (stderr)
none/tests/fdleak_cmsg_supp              (stderr)          New for 
Valgrind-3.24.0.RC1
none/tests/fdleak_cmsg_xml               (stderr)             New for 
Valgrind-3.24.0.RC1
none/tests/fdleak_ipv4_xml               (stderr)               New for 
Valgrind-3.24.0.RC1
none/tests/socket_close_xml              (stderr)             New for 
Valgrind-3.24.0.RC1



PowerPC testing on Power 9, I am seeing 4 additional stderr failures 
versus Valgrind 3.23.0.RC2

  == 767 tests, 7 stderr failures, 0 stdout failures, 13 stderrB 
failures, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo                   (stderrB)
gdbserver_tests/mcblocklistsearch        (stderrB)
gdbserver_tests/mcbreak                  (stderrB)
gdbserver_tests/mcclean_after_fork       (stderrB)
gdbserver_tests/mcinfcallWSRU            (stderrB)
gdbserver_tests/mcleak                   (stderr)
gdbserver_tests/mcleak                   (stderrB)
gdbserver_tests/mcmain_pic               (stderrB)
gdbserver_tests/mcvabits                 (stderrB)
gdbserver_tests/mssnapshot               (stderrB)
gdbserver_tests/nlgone_abrt              (stderrB)
gdbserver_tests/nlgone_exit              (stderrB)
gdbserver_tests/nlgone_return            (stderrB)
gdbserver_tests/nlpasssigalrm            (stderrB)
memcheck/tests/leak-delta                (stderr)
memcheck/tests/linux/rfcomm              (stderr)
none/tests/fdleak_cmsg_supp              (stderr)        New for 
Valgrind-3.24.0.RC1
none/tests/fdleak_cmsg_xml               (stderr)        New for 
Valgrind-3.24.0.RC1
none/tests/fdleak_ipv4_xml               (stderr)        New for 
Valgrind-3.24.0.RC1
none/tests/socket_close_xml              (stderr)        New for 
Valgrind-3.24.0.RC1



PowerPC testing on Power 10, I am seeing 4 additional stderr failures 
versus Valgrind 3.23.0.RC2

== 753 tests, 5 stderr failures, 0 stdout failures, 0 stderrB failures, 
0 stdoutB failures, 0 post failures ==
memcheck/tests/linux/rfcomm              (stderr)
none/tests/fdleak_cmsg_supp (stderr)                      New for 
Valgrind-3.24.0.RC1
none/tests/fdleak_cmsg_xml               (stderr)                      
New for Valgrind-3.24.0.RC1
none/tests/fdleak_ipv4_xml               (stderr)                      
New for Valgrind-3.24.0.RC1
none/tests/socket_close_xml              (stderr)                      
New for Valgrind-3.24.0.RC1

I am not sure what is going on with these tests.  I have not yet been 
able to dig into them.
                                               Carl

On 10/27/24 4:58 PM, Mark Wielaard wrote:
> There are still some pending patches, but lets do an RC1 for some
> wider testing.
>
> An RC1 tarball for 3.24.0 is now available at
> https://sourceware.org/pub/valgrind/valgrind-3.24.0.RC1.tar.bz2
> (md5sum = a11f33c94dcb0f545a27464934b6fef8)
> (sha1sum = b87105b23d3b6d0e212d5729235d0d8225ff8851)
> https://sourceware.org/pub/valgrind/valgrind-3.24.0.RC1.tar.bz2.asc
>
> Please give it a try in configurations that are important for you and
> report any problems you have, either on this mailing list, or
> (preferably) via our bug tracker at
> https://bugs.kde.org/enter_bug.cgi?product=valgrind
>
> If nothing critical emerges a final release will happen on Thursday 31
> October.
>
>
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users