Re: [Valgrind-users] Valgrind-3.23.0.RC1 is available for testing
Carl Love via Valgrind-developers <valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> Tue, 23 Apr 2024 07:09:20 -0700
| Newsgroups | gmane.comp.debugging.valgrind.devel,gmane.comp.debugging.valgrind |
|---|---|
| Message-ID | <[email protected]> |
Mark:
On 4/23/24 05:21, Mark Wielaard wrote:
> Hi Carl,
>
> On Mon, 2024-04-22 at 11:40 -0700, Carl Love wrote:
>> The PowerPC test results for Valgrind 3.23.0.RC1
> Thanks. Looks fairly good overall. I haven't studied the rest, but ...
>
>> none/tests/fdleak_ipv4 (stderr) New failure, did not fail for valgrind 3.22.0
>> none/tests/file_dclose (stderr) New failure, did not fail for valgrind 3.22.0
>> none/tests/socket_close (stderr) New failure, did not fail for valgrind 3.22.0
> These are new tests in 3.23.0 and for some reason they "main" part of
> the stacktrace is slightly different on different systems. I tried to
> work around that with the following commit:
Agreed, I think things look good. I don't see the three new failures as something that should block the release. I am ok with RC1.
Carl