From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: berrange@redhat.com, "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH] docker.py: always use --rm
Date: Thu, 17 Sep 2020 19:50:31 +0100 [thread overview]
Message-ID: <CAHDbmO3_iUbta7ZK6RecMk8zFeMNUngLOuoJoFbH08452-YMzg@mail.gmail.com> (raw)
In-Reply-To: <CABgObfYby_HfevgJ2fP0EDemd4hXbWc24h3C7mZ4ar_N0mE7AQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
Got it.
On Thu, 17 Sep 2020, 17:58 Paolo Bonzini, <pbonzini@redhat.com> wrote:
>
>
> Il gio 17 set 2020, 18:53 Alex Bennée <alex.bennee@linaro.org> ha scritto:
>
>>
>> Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
>>
>> > On 9/17/20 12:44 PM, Paolo Bonzini wrote:
>> >> Avoid that containers pile up.
>> >>
>> >> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> >> ---
>> >> tests/docker/Makefile.include | 1 -
>> >> tests/docker/docker.py | 4 ++--
>> >> 2 files changed, 2 insertions(+), 3 deletions(-)
>> >>
>> >> diff --git a/tests/docker/Makefile.include
>> b/tests/docker/Makefile.include
>> >> index 3daabaa2fd..75704268ff 100644
>> >> --- a/tests/docker/Makefile.include
>> >> +++ b/tests/docker/Makefile.include
>> >> @@ -243,7 +243,6 @@ docker-run: docker-qemu-src
>> >> $(DOCKER_SCRIPT) run \
>> >> $(if $(NOUSER),,--run-as-current-user) \
>> >> --security-opt seccomp=unconfined \
>> >> - $(if $V,,--rm) \
>> >> $(if $(DEBUG),-ti,) \
>> >
>> > Alternatively:
>> >
>> > - $(if $V,,--rm)
>> > - $(if $(DEBUG),-ti,)
>> > + $(if $(DEBUG),-ti,--rm)
>>
>> Surely that should b:
>>
>> $(if $(DEBUG),-ti --rm,)
>>
>> I think being able to keep the container around is useful for debug, I
>> have no problem with changing the behaviour for V=1.
>>
>
> You probably mean $(if $(DEBUG),-ti,--rm) but that would not work because
> the patch adds --rm unconditionally in docker.py. But $(DEBUG) gives you a
> shell to run the test from, so I don't think skipping --rm is useful even
> in the $(DEBUG) case.
>
> Paolo
>
>>
[-- Attachment #2: Type: text/html, Size: 3178 bytes --]
next prev parent reply other threads:[~2020-09-17 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 10:44 [PATCH] docker.py: always use --rm Paolo Bonzini
2020-09-17 10:48 ` Daniel P. Berrangé
2020-09-17 10:49 ` Paolo Bonzini
2020-09-17 10:48 ` no-reply
2020-09-17 10:49 ` no-reply
2020-09-17 13:38 ` Philippe Mathieu-Daudé
2020-09-17 16:52 ` Alex Bennée
2020-09-17 16:58 ` Paolo Bonzini
2020-09-17 18:50 ` Alex Bennée [this message]
2020-09-18 12:36 ` Peter Maydell
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=CAHDbmO3_iUbta7ZK6RecMk8zFeMNUngLOuoJoFbH08452-YMzg@mail.gmail.com \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).