From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: digitalfreak@lingonborough.com, libc-alpha@sourceware.org
Subject: Re: [PATCHv8] nss_db: protect against empty mappings
Date: Fri, 12 Jul 2019 16:19:57 -0400 [thread overview]
Message-ID: <xno91zngya.fsf@greed.delorie.com> (raw)
In-Reply-To: <59540b52-517d-8fff-6634-68cec3ecc0ef@redhat.com> (carlos@redhat.com)
"Carlos O'Donell" <carlos@redhat.com> writes:
> I wonder if we can't make the workflow different, an this is purely
> a psychological thing:
>
> (a) Make a "build done" stamp.
What build? What targets? There are a lot of installable bits in the
testroot that can be built independently. Without a fully
dependency-driven install, it's very hard to detect that "something
changed" which would require a re-install.
Of course, we could check for libc.so itself being newer than
install.stamp, and maybe libm.so if it had containerized tests.
> (b) Compare "build done" stamp with "chroot stamp" and if they are
I suspect this could be centralized into the support routines that
handle exit codes; looking at "/install.stamp" and some other file.
Aside from the problem of reliably creating the "some other file", which
would have to be inside the container also.
next prev parent reply other threads:[~2019-07-12 20:20 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 0:28 nss_db: protect against empty mappings DJ Delorie
2019-06-18 2:35 ` Carlos O'Donell
2019-06-18 3:15 ` DJ Delorie
2019-06-18 3:33 ` Carlos O'Donell
2019-06-18 4:12 ` DJ Delorie
2019-06-18 6:12 ` Florian Weimer
2019-06-18 13:18 ` Carlos O'Donell
2019-06-18 17:47 ` DJ Delorie
2019-06-18 18:15 ` Carlos O'Donell
2019-06-18 18:28 ` [PATCH v4] " DJ Delorie
2019-06-18 18:58 ` [PATCH v5] " DJ Delorie
2019-06-19 7:45 ` Andreas Schwab
2019-06-19 16:31 ` DJ Delorie
2019-06-19 16:33 ` Florian Weimer
2019-06-19 16:56 ` [PATCH V6] " DJ Delorie
2019-06-20 1:02 ` Carlos O'Donell
2019-06-24 8:19 ` Andreas Schwab
2019-06-24 23:51 ` DJ Delorie
2019-06-25 7:56 ` Andreas Schwab
2019-06-25 21:29 ` [PATCHv7] " DJ Delorie
2019-06-25 21:36 ` Florian Weimer
2019-06-28 13:38 ` Florian Weimer
2019-06-28 19:20 ` DJ Delorie
2019-06-28 19:23 ` Florian Weimer
2019-06-28 19:29 ` DJ Delorie
2019-06-28 22:32 ` [PATCHv8] " DJ Delorie
2019-07-08 23:22 ` DJ Delorie
2019-07-10 9:51 ` Florian Weimer
2019-07-10 18:52 ` DJ Delorie
2019-07-12 0:12 ` Rafal Luzynski
2019-07-12 4:21 ` DJ Delorie
2019-07-12 10:24 ` Rafal Luzynski
2019-07-12 11:36 ` Carlos O'Donell
2019-07-12 20:19 ` DJ Delorie [this message]
2019-07-13 2:09 ` Carlos O'Donell
2019-07-13 3:13 ` DJ Delorie
2019-07-18 18:20 ` Carlos O'Donell
2019-07-18 18:44 ` DJ Delorie
2019-07-16 9:54 ` CI/CD in glibc (was: nss_db: protect against empty mappings) Rafal Luzynski
2019-07-16 12:00 ` CI/CD in glibc Florian Weimer
2019-07-16 20:14 ` Carlos O'Donell
2019-07-17 17:58 ` Zack Weinberg
2019-07-17 19:05 ` Florian Weimer
2019-07-12 19:58 ` [PATCHv8] nss_db: protect against empty mappings DJ Delorie
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://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xno91zngya.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=carlos@redhat.com \
--cc=digitalfreak@lingonborough.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).