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

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

Paul:


On 10/29/24 12:38 AM, Paul Floyd via Valgrind-developers wrote:
>
>
> On 28-10-24 19:52, Carl Love via Valgrind-developers wrote:
>> Mark:
>>
>> PowerPC testing on Power 8, I am seeing 4 additional stderr failures 
>> versus Valgrind 3.23.0.RC2
>
>> 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
>
> Hi Carl
>
> It's probably not too serious. The fdleak feature tends to output 
> messages that are highly system dependent and need plenty of filtering 
> in order to have stable regtest results.

Thanks for the feedback.  The tests were run on various lab machines at 
IBM.  I will note that the nightly regression runs on the GCC pool 
machines gcc110 and gcc112 do not have the same failures.

I don't think these failures are an issue for delaying the next 
release.  I agree they do appear to be fairly minor.  I will try and get 
to investigating them soon.

Thanks.

Carl