glibc 2.34 failed tests

[Adhemerval Zanella]

On 03/08/2021 13:15, Michael Brunnbauer wrote:
> 
> hi all,
> 
> these are my test failures for glibc 2.34:
> 
> FAIL: malloc/tst-mxfast-mcheck
> FAIL: malloc/tst-tcfree2
> FAIL: nss/tst-nss-files-hosts-multi
> FAIL: resolv/tst-bug18665
> FAIL: resolv/tst-resolv-search
> FAIL: rt/tst-mqueue10
> FAIL: time/tst-itimer
> 
> In comparison, those failed for 2.33 - which I use in production:
> 
> FAIL: elf/tst-dlopenfail

This is a new failure, could you post the .out output?

> FAIL: malloc/tst-safe-linking

Siddhesh has improved it to avoid some false positives, but from from
the commit message it seems that although unlikely it might still be
possible. Could you post the output to see if this is the case?

> FAIL: malloc/tst-tcfree2

This is another new failure., could you post the .out output as well?

> FAIL: nss/tst-nss-files-hosts-multi
> FAIL: resolv/tst-bug18665
> FAIL: resolv/tst-resolv-search

I recall this might fail depending of how the system network is configured.
What .out file shows?

> 
> Should I worry? Here are the .out files for the new failures:
> 
> cat ./malloc/tst-mxfast-mcheck.out
> tst-mxfast.c:49: numeric comparison failure
>    left: 2 (0x2); from: m.smblks
>   right: 0 (0x0); from: 0
> error: 1 test failures
> 
> cat ./rt/tst-mqueue10.out
> error: tst-mqueue10.c:46: not true: q != (mqd_t) -1
> error: 1 test failures

I think this might be related to the fact rt/tst-mqueue10.c uses the
"/tst-mqueue2-" as template (it might interfere with rt/tst-mqueue2.c
itself).

> 
> cat ./time/tst-itimer.out
> tst-itimer.c:76: numeric comparison failure (widths 64 and 32)
>    left: 10000 (0x2710); from: it_old.it_interval.tv_usec
>   right: 20 (0x14); from: 20
> tst-itimer.c:90: numeric comparison failure
>    left: 20 (0x14); from: it.it_interval.tv_usec
>   right: 10000 (0x2710); from: it_old.it_interval.tv_usec
> tst-itimer.c:118: numeric comparison failure
>    left: 2748779068 (0xa3d70a3c); from: it_old.it_interval.tv_sec
>   right: 8589934591 (0x1ffffffff); from: 0x1ffffffffull
> tst-itimer.c:119: numeric comparison failure (widths 64 and 32)
>    left: 0 (0x0); from: it_old.it_interval.tv_usec
>   right: 20 (0x14); from: 20
> tst-itimer.c:141: numeric comparison failure
>    left: 8589934591 (0x1ffffffff); from: it.it_interval.tv_sec
>   right: 2748779068 (0xa3d70a3c); from: it_old.it_interval.tv_sec
> tst-itimer.c:142: numeric comparison failure
>    left: 20 (0x14); from: it.it_interval.tv_usec
>   right: 0 (0x0); from: it_old.it_interval.tv_usec
> tst-itimer.c:76: numeric comparison failure (widths 64 and 32)
>    left: 10000 (0x2710); from: it_old.it_interval.tv_usec
>   right: 20 (0x14); from: 20
> tst-itimer.c:90: numeric comparison failure
>    left: 20 (0x14); from: it.it_interval.tv_usec
>   right: 10000 (0x2710); from: it_old.it_interval.tv_usec
> tst-itimer.c:118: numeric comparison failure
>    left: 2748779068 (0xa3d70a3c); from: it_old.it_interval.tv_sec
>   right: 8589934591 (0x1ffffffff); from: 0x1ffffffffull
> tst-itimer.c:119: numeric comparison failure (widths 64 and 32)
>    left: 0 (0x0); from: it_old.it_interval.tv_usec
>   right: 20 (0x14); from: 20
> tst-itimer.c:141: numeric comparison failure
>    left: 8589934591 (0x1ffffffff); from: it.it_interval.tv_sec
>   right: 2748779068 (0xa3d70a3c); from: it_old.it_interval.tv_sec
> tst-itimer.c:142: numeric comparison failure
>    left: 20 (0x14); from: it.it_interval.tv_usec
>   right: 0 (0x0); from: it_old.it_interval.tv_usec
> error: 12 test failures

I almost sure this is the same issue I saw on an older kernel under KVM [1]

[1] https://patchwork.sourceware.org/project/glibc/patch/20210719163846.2954193-3-adhemerval.zanella@linaro.org/