From: Thomas Huth <thuth@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Ani Sinha <anisinha@redhat.com>
Cc: "Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] acpi/tests/avocado/bits: enable bios bits avocado tests on gitlab CI pipeline
Date: Mon, 22 May 2023 20:00:14 +0200 [thread overview]
Message-ID: <ddc978a1-8edb-f284-4a45-6d10d1b7733a@redhat.com> (raw)
In-Reply-To: <20230521015057-mutt-send-email-mst@kernel.org>
On 21/05/2023 07.51, Michael S. Tsirkin wrote:
> On Fri, May 19, 2023 at 08:44:18PM +0530, Ani Sinha wrote:
>>
>>
>>> On 17-May-2023, at 12:23 PM, Ani Sinha <anisinha@redhat.com> wrote:
>>>
>>> Biosbits avocado tests on gitlab has thus far been disabled because some
>>> packages needed by this test was missing in the container images used by gitlab
>>> CI. These packages have now been added with the commit:
>>>
>>> da9000784c90d ("tests/lcitool: Add mtools and xorriso and remove genisoimage as dependencies")
>>>
>>> Therefore, this change enables bits avocado test on gitlab.
>>> At the same time, the bits cleanup code has also been made more robust with
>>> this change.
>>>
>>> Signed-off-by: Ani Sinha <anisinha@redhat.com>
>>
>> Michael, did you forget to queue this?
>
>
> Not that I forgot but it takes me time to process new patches.
> This came after I started testing the pull.
FYI, I've picked it up today.
Thomas
next prev parent reply other threads:[~2023-05-22 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 6:53 [PATCH] acpi/tests/avocado/bits: enable bios bits avocado tests on gitlab CI pipeline Ani Sinha
2023-05-19 15:14 ` Ani Sinha
2023-05-21 5:51 ` Michael S. Tsirkin
2023-05-22 18:00 ` Thomas Huth [this message]
2023-05-23 3:13 ` 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=ddc978a1-8edb-f284-4a45-6d10d1b7733a@redhat.com \
--to=thuth@redhat.com \
--cc=anisinha@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).