From: Simon South <simon@simonsouth.net>
To: Bengt Richter <bokr@bokr.com>
Cc: 50346@debbugs.gnu.org
Subject: bug#50346: core-updates-frozen: strace 5.13 fails "make check" on AArch64
Date: Fri, 03 Sep 2021 17:27:41 -0400 [thread overview]
Message-ID: <87tuj1wdrm.fsf@simonsouth.net> (raw)
In-Reply-To: <20210903165335.GA10190@LionPure> (Bengt Richter's message of "Fri, 3 Sep 2021 18:53:35 +0200")
Bengt Richter <bokr@bokr.com> writes:
> Well, that would be the point :)
> I.e., to move the customizations into .conf files and out of
> test-suite sources.
Given the limited flexibility of the test harness I'm not sure there's a
solution that doesn't involve modifying the source, but on reflection
you're right: We actually _do_ expect the test results to differ from
what is provided in the source bundle, so a better solution would be to
update the tests to reflect this rather than to change how they're run.
I'll put together a patch that does that.
Incidentally, the reason for the test failures appears to be the
additional call to _dl_get_origin() added to glibc by the
"glib-dl-cache" patch in commit 52564e9, which produces an additional
readlink/readlinkat syscall strace's test driver isn't expecting. But
this additional call _is_ expected on Guix systems, so the test cases
ought to be modified to match.
--
Simon South
simon@simonsouth.net
next prev parent reply other threads:[~2021-09-03 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 19:24 bug#50346: core-updates-frozen: strace 5.13 fails "make check" on AArch64 Simon South
2021-09-02 22:41 ` Simon South
2021-09-03 12:15 ` Bengt Richter
2021-09-03 14:00 ` Simon South
2021-09-03 16:53 ` Bengt Richter
2021-09-03 21:27 ` Simon South [this message]
2021-09-04 19:51 ` Simon South
2021-09-04 19:58 ` bug#50346: [PATCH core-updates-frozen] gnu: strace: Allow readlink, readlinkat tests to pass Simon South
2021-11-18 13:13 ` bug#50346: core-updates-frozen: strace 5.13 fails "make check" on AArch64 Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tuj1wdrm.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--cc=50346@debbugs.gnu.org \
--cc=bokr@bokr.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).