From: Thomas Huth <thuth@redhat.com>
To: "Michael Tokarev" <mjt@tls.msk.ru>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bin.meng@windriver.com>
Subject: Re: [PATCH] gitlab-ci: Disable the riscv64-debian-cross-container by default
Date: Thu, 12 Oct 2023 14:16:57 +0200 [thread overview]
Message-ID: <82aa015a-ca94-49ce-beec-679cc175b726@redhat.com> (raw)
In-Reply-To: <31a7782f-870b-4ef8-a857-33018b9de0e1@tls.msk.ru>
On 11/10/2023 16.53, Michael Tokarev wrote:
> 11.10.2023 17:42, Thomas Huth wrote:
>> This job is failing since weeks. Let's mark it as manual until
>> it gets fixed.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>
> I was about to sent something like this about a month ago, but
> got distracted.
>
> Acked-by: Michael Tokarev <mjt@tls.msk.ru>
Thanks!
>> ---
>> .gitlab-ci.d/container-cross.yml | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/.gitlab-ci.d/container-cross.yml
>> b/.gitlab-ci.d/container-cross.yml
>> index e0d75d5824..2848166ba3 100644
>> --- a/.gitlab-ci.d/container-cross.yml
>> +++ b/.gitlab-ci.d/container-cross.yml
>> @@ -95,6 +95,7 @@ riscv64-debian-cross-container:
>> allow_failure: true
>> variables:
>> NAME: debian-riscv64-cross
>> + QEMU_JOB_OPTIONAL: 1
>> # we can however build TCG tests using a non-sid base
>> riscv64-debian-test-cross-container:
Drat, looks like I forgot to CC: qemu-devel ... done now, so in case anybody
else has an opinion on this, please let me know!
Thomas
parent reply other threads:[~2023-10-12 12:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <31a7782f-870b-4ef8-a857-33018b9de0e1@tls.msk.ru>]
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=82aa015a-ca94-49ce-beec-679cc175b726@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=mjt@tls.msk.ru \
--cc=palmer@dabbelt.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).