From: Fam Zheng <famz@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, riku.voipio@linaro.org
Subject: Re: [Qemu-devel] [PATCH v5 0/7] docker: Support building qemu-user powered docker test images
Date: Tue, 19 Jul 2016 15:40:47 +0800 [thread overview]
Message-ID: <20160719074047.GJ18103@ad.usersys.redhat.com> (raw)
In-Reply-To: <87shv7ndlo.fsf@linaro.org>
On Mon, 07/18 16:57, Alex Bennée wrote:
> > So any ideas about that?
Hi Alex,
Sorry for the late reply.
>
> Any thoughts on that Fam? Can we merge it without the final step on the
> grounds it makes for useful testing?
Yes, we can, though I'd like to make sure we don't break existing docker tests.
Specifically we need to skip building and spawning the debian-bootstrap image
if its dependencies are not met. To do that we can define a magic exit code for
.pre scripts, and catch it in docker.py.
What do you think?
Fam
>
> >
> > Alex Bennée (5):
> > tests/docker/docker.py: docker_dir outside build
> > tests/docker/docker.py: support --include-executable
> > tests/docker/docker.py: check and run .pre script
> > tests/docker/dockerfiles: new debian-bootstrap.docker
> > tests/docker/docker.py: add update operation
> >
> > Fam Zheng (2):
> > docker: More sensible run script
> > docker: Fix exit code if $CMD failed
> >
> > tests/docker/Makefile.include | 4 +-
> > tests/docker/docker.py | 144 +++++++++++++++++++++--
> > tests/docker/dockerfiles/debian-bootstrap.docker | 21 ++++
> > tests/docker/dockerfiles/debian-bootstrap.pre | 82 +++++++++++++
> > tests/docker/run | 16 ++-
> > 5 files changed, 252 insertions(+), 15 deletions(-)
> > create mode 100644 tests/docker/dockerfiles/debian-bootstrap.docker
> > create mode 100755 tests/docker/dockerfiles/debian-bootstrap.pre
>
>
> --
> Alex Bennée
>
next prev parent reply other threads:[~2016-07-19 7:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 15:00 [Qemu-devel] [PATCH v5 0/7] docker: Support building qemu-user powered docker test images Alex Bennée
2016-07-12 15:00 ` [Qemu-devel] [PATCH v5 1/7] tests/docker/docker.py: docker_dir outside build Alex Bennée
2016-07-12 15:00 ` [Qemu-devel] [PATCH v5 2/7] tests/docker/docker.py: support --include-executable Alex Bennée
2016-07-12 15:00 ` [Qemu-devel] [PATCH v5 3/7] tests/docker/docker.py: check and run .pre script Alex Bennée
2016-07-12 15:00 ` [Qemu-devel] [PATCH v5 4/7] tests/docker/dockerfiles: new debian-bootstrap.docker Alex Bennée
2016-07-12 15:00 ` [Qemu-devel] [PATCH v5 5/7] tests/docker/docker.py: add update operation Alex Bennée
2016-07-12 15:00 ` [Qemu-devel] [PATCH v5 6/7] docker: More sensible run script Alex Bennée
2016-07-12 15:00 ` [Qemu-devel] [PATCH v5 7/7] docker: Fix exit code if $CMD failed Alex Bennée
2016-07-18 15:57 ` [Qemu-devel] [PATCH v5 0/7] docker: Support building qemu-user powered docker test images Alex Bennée
2016-07-19 7:40 ` Fam Zheng [this message]
2016-07-19 8:12 ` Alex Bennée
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=20160719074047.GJ18103@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.