public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/25836] Test container not properly created when running single test
Date: Thu, 16 Apr 2020 14:34:43 +0000	[thread overview]
Message-ID: <bug-25836-131-yWgAWak4yB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25836-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=25836

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2020-04-16
     Ever confirmed|0                           |1

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
This is just a limitation of the implementation of the helper targets.

You could probably detect the container rootfs is missing and generate it, and
then use the stamp to never do that again.

Note: We are still unable to dynamically update the rootfs when the
implementation changes, so that will not be resolved.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2020-04-16 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 14:20 [Bug build/25836] New: " msc at linux dot ibm.com
2020-04-16 14:34 ` carlos at redhat dot com [this message]
2022-06-05  3:55 ` [Bug build/25836] " sam at gentoo dot org

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=bug-25836-131-yWgAWak4yB@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).