From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Ani Sinha <anisinha@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
alex.bennee@linaro.org, philmd@linaro.org, wainersm@redhat.com,
bleal@redhat.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [PATCH 0/2] Add mformat and xorriso dependencies in containers
Date: Thu, 4 May 2023 09:25:33 +0100 [thread overview]
Message-ID: <ZFNr/YMWTicdsVHt@redhat.com> (raw)
In-Reply-To: <82B950B9-1C97-483F-A5A5-C755BEA1B727@redhat.com>
On Thu, May 04, 2023 at 01:52:36PM +0530, Ani Sinha wrote:
>
>
> > On 04-May-2023, at 1:32 PM, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Thu, May 04, 2023 at 08:35:53AM +0200, Thomas Huth wrote:
> >> On 03/05/2023 16.55, Ani Sinha wrote:
> >>> mformat and xorriso tools are needed by biosbits avocado tests. This patchset
> >>> adds those two tools in the docker container images.
> >>
> >> tests/qtest/cdrom-test.c already uses genisoimage to create ISO images, and
> >> the containers already have that tool installed. Could you maybe switch the
> >> biosbits test to use that tool? Or the other way round? ... at least having
> >> two tools to create ISO images in our containers sounds IMHO excessive.
> >
> > It looks like this series wasn't tested,
>
> Oh I wasn’t sure which tests I were to run to verify this because https://www.qemu.org/docs/master/devel/testing.html does not mention any specific tests to run after:
>
> • Once the merge request is accepted, go back to QEMU and update the tests/lcitool/libvirt-ci submodule to point to a commit that contains the mappings.yml update. Then add the prerequisite and run make lcitool-refresh.
>
> Is it “make docker-all-tests” ? Maybe we can update the doc. This is the first time me updating the docker images with new packages and I doing not touch this infrastructure part at all.
By testing, I mean run the CI pipeline in GitLab to see if everything
still passes. I expect the alpine job will fail the container build.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-05-04 8:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 14:55 [PATCH 0/2] Add mformat and xorriso dependencies in containers Ani Sinha
2023-05-03 14:55 ` [PATCH 1/2] tests: libvirt-ci: Update to commit 'c8971e90ac' to pull in mformat and xorriso Ani Sinha
2023-05-03 14:55 ` [PATCH 2/2] tests/lcitool: Add mtools and xorriso as dependency for bios bits avocado tests Ani Sinha
2023-05-04 6:35 ` [PATCH 0/2] Add mformat and xorriso dependencies in containers Thomas Huth
2023-05-04 7:10 ` Ani Sinha
2023-05-04 7:13 ` Thomas Huth
2023-05-04 8:58 ` Daniel P. Berrangé
2023-05-04 9:08 ` Ani Sinha
2023-05-04 8:02 ` Daniel P. Berrangé
2023-05-04 8:22 ` Ani Sinha
2023-05-04 8:25 ` Daniel P. Berrangé [this message]
2023-05-04 11:32 ` Ani Sinha
2023-05-04 8:49 ` Ani Sinha
2023-05-04 9:17 ` Ani Sinha
2023-05-04 9:35 ` Daniel P. Berrangé
2023-05-04 10:13 ` Thomas Huth
2023-05-04 15:56 ` Ani Sinha
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=ZFNr/YMWTicdsVHt@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=anisinha@redhat.com \
--cc=bleal@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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).