From: "Daniel P. Berrangé" <berrange@redhat.com>
To: peterx@redhat.com
Cc: qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>,
Peter Maydell <peter.maydell@linaro.org>,
Eric Auger <eric.auger@redhat.com>,
Sebastian Ott <sebott@redhat.com>
Subject: Re: [PATCH 2/3] ci: Remove tag dependency for build-previous-qemu
Date: Tue, 6 Feb 2024 08:11:58 +0000 [thread overview]
Message-ID: <ZcHpzsLYCPwFPMUq@redhat.com> (raw)
In-Reply-To: <20240206063151.215986-3-peterx@redhat.com>
On Tue, Feb 06, 2024 at 02:31:50PM +0800, peterx@redhat.com wrote:
> From: Peter Xu <peterx@redhat.com>
>
> The new build-previous-qemu job relies on QEMU release tag being present,
> while that may not be always true for personal git repositories since by
> default tag is not pushed. The job can fail on those CI kicks, as reported
> by Peter Maydell.
>
> Fix it by fetching the tags remotely from the official repository, as
> suggested by Dan.
>
> [1] https://lore.kernel.org/r/ZcC9ScKJ7VvqektA@redhat.com
>
> Reported-by: Peter Maydell <peter.maydell@linaro.org>
> Suggested-by: Daniel P. Berrangé <berrange@redhat.com>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> .gitlab-ci.d/buildtest.yml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
> index 79bbc8585b..df48c9d31d 100644
> --- a/.gitlab-ci.d/buildtest.yml
> +++ b/.gitlab-ci.d/buildtest.yml
> @@ -189,6 +189,8 @@ build-previous-qemu:
> TARGETS: x86_64-softmmu aarch64-softmmu
> before_script:
> - export QEMU_PREV_VERSION="$(sed 's/\([0-9.]*\)\.[0-9]*/v\1.0/' VERSION)"
> + - git remote add upstream https://gitlab.com/qemu-project/qemu
> + - git fetch upstream $QEMU_PRRV_VERSION
Typo^^^
> - git checkout $QEMU_PREV_VERSION
> after_script:
> - mv build build-previous
With that typo fixed, then
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-02-06 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 6:31 [PATCH 0/3] ci: Fixes on the recent cross-binary test case peterx
2024-02-06 6:31 ` [PATCH 1/3] tests/migration-test: Stick with gicv3 in aarch64 test peterx
2024-02-06 8:13 ` Daniel P. Berrangé
2024-02-06 6:31 ` [PATCH 2/3] ci: Remove tag dependency for build-previous-qemu peterx
2024-02-06 8:11 ` Daniel P. Berrangé [this message]
2024-02-06 8:30 ` Peter Xu
2024-02-06 6:31 ` [PATCH 3/3] ci: Update comment for migration-compat-aarch64 peterx
2024-02-06 8:12 ` Daniel P. Berrangé
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=ZcHpzsLYCPwFPMUq@redhat.com \
--to=berrange@redhat.com \
--cc=eric.auger@redhat.com \
--cc=farosas@suse.de \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sebott@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).