From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Add --disable-test-container to disable test container
Date: Mon, 5 Feb 2024 07:38:14 -0800 [thread overview]
Message-ID: <CAMe9rOoRiJkSZyDLSnUjp+WNWMzGXV5b4_O8vg6eEnfSzxDVcA@mail.gmail.com> (raw)
In-Reply-To: <87r0hr2adj.fsf@oldenburg.str.redhat.com>
On Mon, Feb 5, 2024 at 7:34 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * H. J. Lu:
>
> > On Mon, Feb 5, 2024 at 6:46 AM Florian Weimer <fweimer@redhat.com> wrote:
> >>
> >> * H. J. Lu:
> >>
> >> > It can be difficult to run tests in container under simulator. Add
> >> > --disable-test-container configure option to disable test container.
> >> > Container tests are enabled by default.
> >>
> >> I think we should compile the test-in-container tests. One way to get
> >> that might be to build support/test-container.c in such a way that it
> >> always returns 77.
> >
> > Make all test-wrapper unsupported? Or add an emulator test-wrapper
> > option and make only emulator test-wrapper unsupported?
>
> I meant support/test-container.c specifically, not test-wrapper.
>
SDE is transparent to programs. How does support/test-container.c
know that it is running under SDE?
--
H.J.
next prev parent reply other threads:[~2024-02-05 15:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 18:55 H.J. Lu
2024-02-05 13:55 ` Adhemerval Zanella Netto
2024-02-05 14:41 ` H.J. Lu
2024-02-05 14:54 ` Adhemerval Zanella Netto
2024-02-05 15:20 ` H.J. Lu
2024-02-05 14:46 ` Florian Weimer
2024-02-05 15:22 ` H.J. Lu
2024-02-05 15:34 ` Florian Weimer
2024-02-05 15:38 ` H.J. Lu [this message]
2024-02-05 15:44 ` Florian Weimer
2024-02-05 15:51 ` H.J. Lu
2024-02-05 15:48 ` Andreas Schwab
2024-02-05 15:50 ` H.J. Lu
2024-02-05 15:57 ` Andreas Schwab
2024-02-05 16:19 ` H.J. Lu
2024-02-05 15:51 ` Adhemerval Zanella Netto
2024-02-05 15:55 ` Florian Weimer
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=CAMe9rOoRiJkSZyDLSnUjp+WNWMzGXV5b4_O8vg6eEnfSzxDVcA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=fweimer@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).