public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stli at linux dot ibm.com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nss/27537] [2.33/2.34 Regression] FAIL: nss/tst-reload2 Date: Thu, 11 Mar 2021 08:25:09 +0000 [thread overview] Message-ID: <bug-27537-131-aZ5u5Mr5al@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27537-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27537 Stefan Liebler <stli at linux dot ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stli at linux dot ibm.com --- Comment #9 from Stefan Liebler <stli at linux dot ibm.com> --- I'm getting the same output if running this sequence: $ cd <builddir> $ rm -f testroot.root/etc/nsswitch.conf $ make t=nss/tst-reload1 test PASS: nss/tst-reload1 $ cat testroot.root/etc/nsswitch.conf passwd: test2 group: test2 hosts: test2 $ make t=nss/tst-reload2 test tst-reload2.c:112: numeric comparison failure left: 5 (0x5); from: pw->pw_uid right: 1234 (0x4d2); from: 1234 error: tst-reload2.c:130: not true: pw->pw_uid != 2468 tst-reload2.c:136: numeric comparison failure left: 5 (0x5); from: pw->pw_uid right: 1234 (0x4d2); from: 1234 error: tst-reload2.c:146: not true: he != NULL error: 4 test failures $ cat testroot.root/etc/nsswitch.conf passwd: test2 group: test2 hosts: test2 According to tst-reload2.c and current nsswitch.conf, it is using pwd_table2, which is PWD_N (5, "test1"). According to the nss/tst-reload2.root/etc/nsswitch.conf, it should use PWD_N (1234, "test1") of pwd_table1. testroot.root/etc/nsswitch.conf was not synced by support/test-container.c as the size (40 bytes) and timestamp (in case of a fresh git clone) of nsswitch.conf files does not differ, but its content: nss/tst-reload1.root/etc/nsswitch.conf nss/tst-reload1.root/etc/nsswitch.conf2 nss/tst-reload2.root/etc/nsswitch.conf nss/tst-reload2.root/subdir/etc/nsswitch.conf You will also see fails if rerunning nss/tst-reload1 multiple times. See discussion on mailing-list: "[PATCH] Ensure that nsswitch.conf for nss/tst-reload[12] are really synced." https://sourceware.org/pipermail/libc-alpha/2021-March/123614.html Note: I have not checked if this is also the case for nss/tst-nss-files-hosts-long. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-11 8:25 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-06 17:45 [Bug nss/27537] New: [2.33 " hjl.tools at gmail dot com 2021-03-08 8:08 ` [Bug nss/27537] " fweimer at redhat dot com 2021-03-08 13:11 ` hjl.tools at gmail dot com 2021-03-08 13:34 ` fweimer at redhat dot com 2021-03-08 15:15 ` hjl.tools at gmail dot com 2021-03-08 16:17 ` skpgkp2 at gmail dot com 2021-03-08 17:39 ` skpgkp2 at gmail dot com 2021-03-08 17:57 ` schwab@linux-m68k.org 2021-03-09 19:08 ` [Bug nss/27537] [2.33/2.34 " hjl.tools at gmail dot com 2021-03-09 20:09 ` dj at redhat dot com 2021-03-09 21:06 ` hjl.tools at gmail dot com 2021-03-10 14:38 ` hjl.tools at gmail dot com 2021-03-11 8:25 ` stli at linux dot ibm.com [this message] 2021-03-11 22:08 ` dj at redhat dot com
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=bug-27537-131-aZ5u5Mr5al@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).