From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] .gitlab-ci.d/cirrus.yml: Fix the NetBSD and OpenBSD Cirrus-CI KVM jobs
Date: Wed, 24 Apr 2024 09:23:12 +0100 [thread overview]
Message-ID: <ZijBcG5hnr_8rFPS@redhat.com> (raw)
In-Reply-To: <20240424074202.245646-1-thuth@redhat.com>
On Wed, Apr 24, 2024 at 09:42:02AM +0200, Thomas Huth wrote:
> Pulling the "master" libvirt-ci containers does not work anymore,
> so we have to switch to the "latest" instead. See also:
> https://gitlab.com/libvirt/libvirt/-/commit/5d591421220c850aa64a640
> https://gitlab.com/libvirt/libvirt-ci/-/commit/6e3c5ccac77714be70c0
>
> The effects were dormant for a year as the old ':master' tags were
> not removed until some weeks ago.
>
> The other Cirrus-CI jobs were already fixed in commit 1d2f2b35bc86b7a1
> ("gitlab-ci/cirrus: switch from 'master' to 'latest'"), but apparently
> nobody noticed the KVM jobs so far that need to be triggered manually.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> .gitlab-ci.d/cirrus.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
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:[~2024-04-24 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 7:42 [PATCH] .gitlab-ci.d/cirrus.yml: Fix the NetBSD and OpenBSD Cirrus-CI KVM jobs Thomas Huth
2024-04-24 8:23 ` Daniel P. Berrangé [this message]
2024-04-24 8:37 ` Philippe Mathieu-Daudé
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=ZijBcG5hnr_8rFPS@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).