From: Michael Brunnbauer <brunni@netestate.de>
To: libc-help@sourceware.org
Subject: glibc 2.34 failed tests
Date: Tue, 3 Aug 2021 18:15:39 +0200 [thread overview]
Message-ID: <YQlrqxFEjkB1F/4/@netestate.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 3244 bytes --]
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
FAIL: malloc/tst-safe-linking
FAIL: malloc/tst-tcfree2
FAIL: nss/tst-nss-files-hosts-multi
FAIL: resolv/tst-bug18665
FAIL: resolv/tst-resolv-search
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
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
thnx,
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 reply other threads:[~2021-08-03 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 16:15 Michael Brunnbauer [this message]
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
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=YQlrqxFEjkB1F/4/@netestate.de \
--to=brunni@netestate.de \
--cc=libc-help@sourceware.org \
/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).