On Mon, 28 Nov 2016 11:24:27 -0200 Breno Leitao <[email protected]> wrote:
On 11/27/2016 07:16 PM, Ghislain Vaillant wrote:
> On Thu, 24 Nov 2016 18:49:29 -0200 Breno Leitao <[email protected]> wrote:
>> I am looking at this issue, and the first test set is checkall.
>>
>> If I run it inside dpkg-buildpackage, it fails as in the log, but, if I run
>> it isolated, I see no errors, as showed:
>>
>> $ ./checkall 2>&1 | grep -i fail
>> $
>>
>> Looking all tests I see "-> OK". Anyway, I am continue to debug what is the
>> problem here.
>
> It could be a lucky shot. Have you tried running them multiple times?
Yes, and it works, but it fails when running in multi thread mode. Anyway, I
am able to reproduce the problem here.
Ack.
> If you look carefully at the log you will find that some tests have an
> unrealistically low tolerance value (in the order of 1E-322), which make them
> succeed when the difference is exactly 0 and fail otherwise.
That is interesting, Float precision might be a platform characterstic,
mainly if using long double, or, quad float precision.
Anyway, I will go deeper in the code to understand the problem here.
I might eventually just bypass testing for ppc64el to let the package
transition to testing, unless you think you are gonna have a fix ready
very soon. With the transition window extended to 10 days and the
soft-freeze deadline happening, I cannot wait for very much longer.
Please keep me up-to-date, and thanks for investigating.
Ghis