From: Michael Brunnbauer <brunni@netestate.de>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-help@sourceware.org, Siddhesh Poyarekar <siddhesh@redhat.com>
Subject: Re: glibc 2.34 failed tests
Date: Wed, 4 Aug 2021 14:29:51 +0200 [thread overview]
Message-ID: <YQqIPzRbhrC84yrQ@netestate.de> (raw)
In-Reply-To: <d2b5a422-89cd-9401-cee6-38e58bd7c0f0@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 4754 bytes --]
hi
On Wed, Aug 04, 2021 at 08:56:17AM -0300, Adhemerval Zanella wrote:
> > FAIL: elf/tst-dlopenfail
>
> This is a new failure, could you post the .out output?
>
> > FAIL: malloc/tst-safe-linking
Those two failures occured with glibc 2.33 but not with 2.34 on my current
machine.
> > FAIL: malloc/tst-tcfree2
>
> This is another new failure., could you post the .out output as well?
FAIL: tcache double free
Expected signal 'Aborted' from child, got none
> > 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?
It's an ipv4 only system. Here are the outputs:
cat nss/tst-nss-files-hosts-multi.out
Timed out: killed the child process
Termination time: 2021-08-03T15:50:02.888711343
Last write to standard output: 2021-08-03T15:49:22.870384035
cat resolv/tst-bug18665.out
warning: unshare (CLONE_NEWUTS) failed: Invalid argument
warning: could not enter network namespace
Timed out: killed the child process
Termination time: 2021-08-03T15:48:22.269459412
Last write to standard output: 2021-08-03T15:48:02.250298068
cat resolv/tst-resolv-search.out
warning: unshare (CLONE_NEWUTS) failed: Invalid argument
warning: could not enter network namespace
Timed out: killed the child process
Termination time: 2021-08-03T15:48:52.829291960
Last write to standard output: 2021-08-03T15:48:32.810330616
> > 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).
I opened a ticket for this one: https://sourceware.org/bugzilla/show_bug.cgi?id=28188
> > 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/
My machine is not a virtual one though. Here is the ticket for this one:
https://sourceware.org/bugzilla/show_bug.cgi?id=28189
cu,
brunni
--
++ Michael Brunnbauer
++ netEstate GmbH
++ Geisenhausener Straße 11a
++ 81379 München
++ Tel +49 89 32 19 77 80
++ Fax +49 89 32 19 77 89
++ E-Mail brunni@netestate.de
++ https://www.netestate.de/
++
++ Sitz: München, HRB Nr.142452 (Handelsregister B München)
++ USt-IdNr. DE221033342
++ Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer
++ Prokurist: Dipl. Kfm. (Univ.) Markus Hendel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-08-04 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 16:15 Michael Brunnbauer
2021-08-03 16:32 ` Siddhesh Poyarekar
2021-08-04 11:56 ` Adhemerval Zanella
2021-08-04 12:00 ` Siddhesh Poyarekar
2021-08-04 12:03 ` Adhemerval Zanella
2021-08-04 12:08 ` Siddhesh Poyarekar
2021-08-04 12:10 ` Adhemerval Zanella
2021-08-04 12:12 ` Siddhesh Poyarekar
2021-08-04 12:29 ` Michael Brunnbauer [this message]
2021-08-04 20:12 ` Adhemerval Zanella
2021-08-05 11:13 ` Michael Brunnbauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YQqIPzRbhrC84yrQ@netestate.de \
--to=brunni@netestate.de \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-help@sourceware.org \
--cc=siddhesh@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).