Re: Valgrind-3.27.0.RC1 is available for testing
Abhay Kandpal via Valgrind-developers <valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> Thu, 16 Apr 2026 12:51:49 +0530
| Newsgroups | gmane.comp.debugging.valgrind.devel,gmane.comp.debugging.valgrind |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============6612313789415265593==
Content-Type: multipart/alternative;
boundary="------------m0MzZcz4Gfc1CC1pTBwIQ3d8"
Content-Language: en-GB
This is a multi-part message in MIME format.
--------------m0MzZcz4Gfc1CC1pTBwIQ3d8
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Mark,
We tested Valgrind 3.27 RC1 across Power systems.
Platform
Fixed Failures
New Failures
Power10 LE
memcheck/tests/descr_belowsp (stderr)
memcheck/tests/linux/rfcomm (stderr)
drd/tests/getaddrinfo (stderr)
none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)
None
Power10 BE
none/tests/socket_close_xml (stderr)
none/tests/fdleak_cmsg_xml (stderr)
memcheck/tests/linux/ioctl_procmap_query (stdout)
memcheck/tests/linux/ioctl_procmap_query (stderr)
memcheck/tests/replaces_malloc_client_req (stdout)
memcheck/tests/replaces_malloc_client_req (stderr)
memcheck/tests/threadname_xml (stderr)
Power9 LE
none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)
memcheck/tests/linux/rfcomm (stderr)
Power9 BE
none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)
none/tests/fdleak_ipv4 (stderr)
none/tests/fdleak_ipv4_xml (stderr)
none/tests/fdleak_ipv4_xml (stdout)
Power8 LE
none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)
memcheck/tests/replaces_malloc_client_req (stdout)
memcheck/tests/replaces_malloc_client_req (stderr)
memcheck/tests/nothing_xml (stderr)
memcheck/tests/simple_leak_xml (stderr)
memcheck/tests/simple_reachable_xml (stderr)
memcheck/tests/threadname_xml (stderr)
memcheck/tests/xmas_tree_xml (stderr)
Power8 BE
none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)
memcheck/tests/linux/ioctl_procmap_query (stdout)
memcheck/tests/linux/ioctl_procmap_query (stderr)
memcheck/tests/replaces_malloc_client_req. (stdout)
memcheck/tests/replaces_malloc_client_req. (stderr)
memcheck/tests/threadname_xml (stderr)
Overall, several previously failing tests are now fixed.
A small number of new failures are observed, primarily on BE systems and older processors, and are not considered release blockers.
From our side, there are no blockers for the 3.27 release.
We will investigate the new failures post-release.
Regards
Abhay Kandpal
On 14/04/26 06:37, Mark Wielaard wrote:
> An RC1 tarball for 3.27.0 is now available at
> https://sourceware.org/pub/valgrind/valgrind-3.27.0.RC1.tar.bz2
> (md5sum = bd95111c1a9f81f136c5e4e2c62b493e)
> (sha1sum = 0eefb3a7d86a3bd0154480db3d2173bb8bd6d7c1)
> https://sourceware.org/pub/valgrind/valgrind-3.27.0.RC1.tar.bz2.asc
> Public keys can be found athttps://www.klomp.org/mark/gnupg-pub.txt
>
> 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
>
> An RC2 should be available Fri Apr 17
> The final 3.27.0 release is scheduled for Mon Apr 20.
>
>
> _______________________________________________
> Valgrind-developers mailing list
> Valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
--------------m0MzZcz4Gfc1CC1pTBwIQ3d8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<pre data-start="193" data-end="201">Hi Mark,</pre>
<pre data-start="203" data-end="252">We tested Valgrind 3.27 RC1 across Power systems.
</pre>
<table cellpadding="2" cellspacing="2" border="1" width="343"
height="279">
<tbody>
<tr>
<td valign="top">
<pre>Platform</pre>
</td>
<td valign="top">
<pre>Fixed Failures</pre>
</td>
<td valign="top">
<pre>New Failures</pre>
</td>
</tr>
<tr>
<td valign="top">
<pre>Power10 LE</pre>
</td>
<td valign="top">
<pre>memcheck/tests/descr_belowsp (stderr)
memcheck/tests/linux/rfcomm (stderr)
drd/tests/getaddrinfo (stderr)
none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)</pre>
</td>
<td valign="top">
<pre>None</pre>
</td>
</tr>
<tr>
<td valign="top">
<pre>Power10 BE</pre>
</td>
<td valign="top">
<pre>none/tests/socket_close_xml (stderr)
none/tests/fdleak_cmsg_xml (stderr)</pre>
</td>
<td valign="top">
<pre>memcheck/tests/linux/ioctl_procmap_query (stdout)
memcheck/tests/linux/ioctl_procmap_query (stderr)
memcheck/tests/replaces_malloc_client_req (stdout)
memcheck/tests/replaces_malloc_client_req (stderr)
memcheck/tests/threadname_xml (stderr)</pre>
</td>
</tr>
<tr>
<td valign="top">
<pre>Power9 LE</pre>
</td>
<td valign="top">
<pre>none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)</pre>
</td>
<td valign="top">
<pre>memcheck/tests/linux/rfcomm (stderr)
</pre>
</td>
</tr>
<tr>
<td valign="top">
<pre>Power9 BE</pre>
</td>
<td valign="top">
<pre>none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)</pre>
</td>
<td valign="top">
<pre>none/tests/fdleak_ipv4 (stderr)
none/tests/fdleak_ipv4_xml (stderr)
none/tests/fdleak_ipv4_xml (stdout)</pre>
</td>
</tr>
<tr>
<td valign="top">
<pre>Power8 LE</pre>
</td>
<td valign="top">
<pre>none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)
</pre>
</td>
<td valign="top">
<pre>memcheck/tests/replaces_malloc_client_req (stdout)
memcheck/tests/replaces_malloc_client_req (stderr)
memcheck/tests/nothing_xml (stderr)
memcheck/tests/simple_leak_xml (stderr)
memcheck/tests/simple_reachable_xml (stderr)
memcheck/tests/threadname_xml (stderr)
memcheck/tests/xmas_tree_xml (stderr)</pre>
</td>
</tr>
<tr>
<td valign="top">
<pre>Power8 BE
</pre>
</td>
<td valign="top">
<pre>none/tests/fdleak_cmsg_xml (stderr)
none/tests/socket_close_xml (stderr)</pre>
</td>
<td valign="top">
<pre>memcheck/tests/linux/ioctl_procmap_query (stdout)
memcheck/tests/linux/ioctl_procmap_query (stderr)
memcheck/tests/replaces_malloc_client_req. (stdout)
memcheck/tests/replaces_malloc_client_req. (stderr)
memcheck/tests/threadname_xml (stderr)</pre>
</td>
</tr>
</tbody>
</table>
<pre data-start="203" data-end="252">
</pre>
<pre data-start="1015" data-end="1203">Overall, several previously failing tests are now fixed.
A small number of new failures are observed, primarily on BE systems and older processors, and are not considered release blockers.</pre>
<pre data-start="1205" data-end="1263">From our side, there are no blockers for the 3.27 release.</pre>
<pre data-start="1265" data-end="1315">We will investigate the new failures post-release.</pre>
<pre data-section-id="1diqeah" data-start="254" data-end="276">
Regards
Abhay Kandpal</pre>
<pre>
</pre>
<pre class="moz-cite-prefix">On 14/04/26 06:37, Mark Wielaard wrote:
</pre>
<blockquote type="cite"
cite="mid:20260414010708.GE4979-ccHWXNLP7XmvZOhXRs0CNB2eb7JE58TQ@public.gmane.org">
<pre wrap="" class="moz-quote-pre">An RC1 tarball for 3.27.0 is now available at
<a class="moz-txt-link-freetext" href="https://sourceware.org/pub/valgrind/valgrind-3.27.0.RC1.tar.bz2">https://sourceware.org/pub/valgrind/valgrind-3.27.0.RC1.tar.bz2</a>
(md5sum = bd95111c1a9f81f136c5e4e2c62b493e)
(sha1sum = 0eefb3a7d86a3bd0154480db3d2173bb8bd6d7c1)
<a class="moz-txt-link-freetext" href="https://sourceware.org/pub/valgrind/valgrind-3.27.0.RC1.tar.bz2.asc">https://sourceware.org/pub/valgrind/valgrind-3.27.0.RC1.tar.bz2.asc</a>
Public keys can be found at <a class="moz-txt-link-freetext" href="https://www.klomp.org/mark/gnupg-pub.txt">https://www.klomp.org/mark/gnupg-pub.txt</a>
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
<a class="moz-txt-link-freetext" href="https://bugs.kde.org/enter_bug.cgi?product=valgrind">https://bugs.kde.org/enter_bug.cgi?product=valgrind</a>
An RC2 should be available Fri Apr 17
The final 3.27.0 release is scheduled for Mon Apr 20.
_______________________________________________
Valgrind-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org">Valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/valgrind-developers">https://lists.sourceforge.net/lists/listinfo/valgrind-developers</a>
</pre>
</blockquote>
</body>
</html>
--------------m0MzZcz4Gfc1CC1pTBwIQ3d8--
--===============6612313789415265593==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============6612313789415265593==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Valgrind-developers mailing list
Valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
--===============6612313789415265593==--