From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>, DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] test-in-container: Install locales into the test container
Date: Tue, 09 Jul 2019 21:08:00 -0000 [thread overview]
Message-ID: <8c64089e-c44c-db20-1a80-562e009d2d42@redhat.com> (raw)
In-Reply-To: <87sgrfc4n5.fsf@oldenburg2.str.redhat.com>
On 7/9/19 4:52 PM, Florian Weimer wrote:
> I think applying this patch as-is would make glibc development
> substantially more difficult for me.
Where do you draw the line? Eventually the testing is going to
slow down your edit/build/test cycle. If this is a problem for
developers then we need some kind of objective "line" that we
try not to cross.
Should we have a staggered approach?
make check-sanity
-- Run as many tests as fit into 10s.
-- Run all tests which are not support_become_root,
test-in-container, or xcheck tests, since these
can be expensive.
make check
-- No time limit for testing.
-- Run all tests which are not xcheck tests.
make xhceck
-- No time limit for testing.
-- Run all tests including xcheck tests.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-07-09 21:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 17:32 Florian Weimer
2019-07-09 18:07 ` DJ Delorie
2019-07-09 20:52 ` Florian Weimer
2019-07-09 20:59 ` DJ Delorie
2019-07-09 21:02 ` Florian Weimer
2019-07-09 21:11 ` Partial test suite run builds corrupt test-in-container testroot Carlos O'Donell
2019-07-10 0:36 ` DJ Delorie
2019-07-10 5:50 ` Florian Weimer
2019-07-10 16:34 ` DJ Delorie
2019-07-10 16:35 ` Florian Weimer
2019-07-10 16:38 ` DJ Delorie
2019-07-19 11:52 ` Florian Weimer
2019-07-22 20:45 ` [PATCH] test-container: Install with $(all-subdirs) [BZ #24794] Tulio Magno Quites Machado Filho
2019-07-22 20:56 ` DJ Delorie
2019-07-23 16:29 ` Tulio Magno Quites Machado Filho
2019-07-24 14:48 ` Stefan Liebler
2019-07-24 15:32 ` Tulio Magno Quites Machado Filho
2019-07-24 20:40 ` Carlos O'Donell
2019-07-24 23:50 ` DJ Delorie
2019-07-25 0:03 ` [PATCH] test-container: Install with $(sorted-subdirs) " Tulio Magno Quites Machado Filho
2019-07-25 1:32 ` DJ Delorie
2019-07-25 12:46 ` Szabolcs Nagy
2019-07-25 12:56 ` Carlos O'Donell
2019-07-29 13:36 ` Tulio Magno Quites Machado Filho
2022-01-27 15:25 ` H.J. Lu
2019-07-25 13:24 ` Stefan Liebler
2019-07-09 21:08 ` Carlos O'Donell [this message]
2019-07-09 23:55 ` [PATCH] test-in-container: Install locales into the test container DJ Delorie
2019-07-12 4:02 ` Carlos O'Donell
2019-07-12 5:49 ` 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=8c64089e-c44c-db20-1a80-562e009d2d42@redhat.com \
--to=carlos@redhat.com \
--cc=dj@redhat.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).