From: Thomas Huth <thuth@redhat.com>
To: AL Yu-Chen Cho <acho@suse.com>, qemu-devel@nongnu.org
Cc: fam@euphon.net, lyan@suse.com, philmd@redhat.com,
wainersm@redhat.com, brogers@suse.com, cfontana@suse.de,
alex.bennee@linaro.org
Subject: Re: [PATCH v2] gitlab-ci.yml: Add openSUSE Leap 15.2 for gitlab CI/CD
Date: Fri, 11 Dec 2020 14:09:07 +0100 [thread overview]
Message-ID: <926da98d-e885-31b1-3e05-a06d37a24947@redhat.com> (raw)
In-Reply-To: <ec5b267368e6b1936b697b8190aa04325f5aa673.camel@suse.com>
On 10/12/2020 10.32, AL Yu-Chen Cho wrote:
> Hi Thomas,
>
> I try to reproduce this failed in my repo, but it seems works fine.
> Would you please give it a try again? I think you maybe just hit a bad
> point in time...
I just re-tried, but it still fails for me:
https://gitlab.com/huth/qemu/-/jobs/905376471
Did you also rebase your branch to the latest master version?
Thomas
next prev parent reply other threads:[~2020-12-11 13:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 11:30 [PATCH] gitlab-ci.yml: Add openSUSE Tumbleweed and Leap for gitlab CI/CD Yu-Chen, Cho
2020-11-16 12:19 ` Alex Bennée
2020-11-17 6:19 ` AL Yu-Chen Cho
2020-11-17 6:57 ` [PATCH] gitlab-ci.yml: Add openSUSE Leap 15.2 " Cho, Yu-Chen
2020-11-17 11:51 ` Thomas Huth
2020-11-19 7:37 ` AL Yu-Chen Cho
2020-11-19 9:29 ` Daniel P. Berrangé
2020-11-19 10:34 ` Alex Bennée
2020-11-24 9:45 ` [PATCH v2] " Cho, Yu-Chen
2020-12-08 6:55 ` Thomas Huth
2020-12-08 8:25 ` AL Yu-Chen Cho
2020-12-10 9:32 ` AL Yu-Chen Cho via
2020-12-11 13:09 ` Thomas Huth [this message]
2020-12-18 10:56 ` Thomas Huth
2020-12-24 8:55 ` Cho Yu-Chen
-- strict thread matches above, loose matches on Subject: below --
2020-11-30 4:26 Cho, Yu-Chen
2020-11-30 8:28 ` Thomas Huth
2020-11-30 9:11 ` Philippe Mathieu-Daudé
2020-11-30 9:14 ` Philippe Mathieu-Daudé
2020-12-03 3:38 ` AL Yu-Chen Cho
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=926da98d-e885-31b1-3e05-a06d37a24947@redhat.com \
--to=thuth@redhat.com \
--cc=acho@suse.com \
--cc=alex.bennee@linaro.org \
--cc=brogers@suse.com \
--cc=cfontana@suse.de \
--cc=fam@euphon.net \
--cc=lyan@suse.com \
--cc=philmd@redhat.com \
--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).