From: DJ Delorie <dj@redhat.com>
To: libc-alpha@sourceware.org
Subject: making the testsuite more like real life... ld.so edition
Date: Wed, 16 Oct 2019 21:00:00 -0000 [thread overview]
Message-ID: <xneezch0dk.fsf@greed.delorie.com> (raw)
I just finished RCA'ing a bugzilla[*] where the fault depended on
(among other things outside the scope of this email) the fact that we
run ld.so directly, instead of indirectly. I.e. these two commands
produce different results:
$ ld.so tst-foo
$ tst.foo
What are our options for running those types of tests in a more "real
world" way?
Should we modify all the test-in-container tests to drop the explicit
ld.so, and relegate those tests to t-i-c?
Should we modify how we build the tests so that we never need the
explicit ld.so?
Other ideas?
[*] https://bugzilla.redhat.com/show_bug.cgi?id=1653942
reply other threads:[~2019-10-16 21:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=xneezch0dk.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=libc-alpha@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).