Hi Jeevitha, On Fri, 2025-04-25 at 11:52 +0000, P Jeevitha wrote: > Hi Everyone, > > valgrind-3.25.0.RC1 looks good on Power and that there are no issues > requiring fixes before releasing Valgrind 3.25
Thanks so much for testing. The results do indeed look good. I am going to prepare the 3.25.0 final release now. I didn't see your message on the list, I am not sure why not. Maybe because you are not subscribed, or because the message used HTML? So I'll quote it in full below just to make sure others are aware of your testing efforts. Thanks, Mark > The PowerPC testsults for Both LE & BE are as follows > > Powerpc64LE Results: > > Power8: > > There are no new failures compared to Valgrind 3.24.0. > > > > == 768 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0 > stdoutB failures, 3 post failures == > > memcheck/tests/leak_cpp_interior (stderr) > > memcheck/tests/linux/rfcomm (stderr) > > memcheck/tests/linux/sys-execveat (stderr) > > massif/tests/bug469146 (post) > > massif/tests/new-cpp (post) > > massif/tests/overloaded-new (post) > > > > > > Power9: > > There are no new failures compared to Valgrind 3.24.0. > > > > == 775 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 > stdoutB failures, 0 post failures == > > memcheck/tests/linux/rfcomm (stderr) > > > > > > Power10: > > There are no new failures compared to Valgrind 3.24.0. > > > > == 781 tests, 7 stderr failures, 2 stdout failures, 0 stderrB failures, 0 > stdoutB failures, 0 post failures == > > memcheck/tests/execve1 (stderr) > > memcheck/tests/execve2 (stderr) > > memcheck/tests/linux/rfcomm (stderr) > > memcheck/tests/thread_alloca (stderr) > > helgrind/tests/getaddrinfo (stderr) > > drd/tests/getaddrinfo (stderr) > > none/tests/allexec32 (stdout) > > none/tests/allexec64 (stdout) > > none/tests/scripts/shell (stderr) > > > > > > > > > > PowerpcBE Results: > > > > Power8: > > There are 2 new stderr failures and 1 new stdout failure compared to Valgrind > 3.24.0, as these are newly added tests. However these can be safely ignored > as they were not reproduced on Power9. > > Apart from previous expected failures from baseline , below are the > additional failures. > > > > == 785 tests, 333 stderr failures, 70 stdout failures, 3 stderrB failures, 3 > stdoutB failures, 6 post failures == > > > > memcheck/tests/cdebug_zstd (stderr) > > memcheck/tests/wcscat (stdout) > > memcheck/tests/wcscat (stderr) > > > > > > Note: These test cases are failing due to missing symbols from certain > packages. However, the issue is not reproducible on Power9. > > > > Power9: > > There are no new failures compared to Valgrind 3.24.0. > > > > == 819 tests, 52 stderr failures, 45 stdout failures, 1 stderrB failure, 2 > stdoutB failures, 2 post failures == > > > > Thanks, > > Jeevitha > > > > > > > > > > > > ------------------------------------------------------------------------------------------------------------------ > Subject: [Valgrind-developers] Valgrind-3.25.0.RC1 is available for > testing > Date: Fri, 18 Apr 2025 15:53:59 +0200 > From: Mark Wielaard <m...@klomp.org> > To: valgrind-develop...@lists.sourceforge.net, > valgrind-users@lists.sourceforge.net > > > > Slightly later than originally planned, but the RC1 is finally out! > > An RC1 tarball for 3.25.0 is now available at > https://sourceware.org/pub/valgrind/valgrind-3.25.0.RC1.tar.bz2 > (md5sum = 2f02fe951278ebde62bba65c3a311a40) > (sha1sum = 3679ddc3237455f07de0ae30f21e947868c2218e) > https://sourceware.org/pub/valgrind/valgrind-3.25.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 > > The NEWS file isn't complete up to date yet, but some highlights: > > - Initial RISCV64/Linux support. > - Valgrind gdbserver supports 'x' packets. > - Numerous bug fixes for Illumos. > - --track-fds=yes now treats all inherited file descriptors like > stdin/out/err (0,1,2) and there is a --modify-fds=high option. > - s390x support for various new instructions (BPP, BPRP and NIAI) > - Various new linux syscalls are supported (landlock*, open_tree, > move_mount, fsopen, fsconfig, fsmount, fspick, userfaultfd) > - The Linux Test Project (ltp) is integrated in the testsuite > try 'make ltpchecks' (this will take a while and will point out > various missing syscalls and valgrind crashes!) > > Since this RC1 is slightly later than planned and it is a long Easter > weekend for those that celebrate, lets do the RC2 on Wed Apr 25, with > the 3.25.0 final on Fri Apr 27. > > > _______________________________________________ > Valgrind-developers mailing list > valgrind-develop...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/valgrind-developers _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
