From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: gitlab build-edk2 failures
Date: Sun, 17 Oct 2021 16:58:37 +0200 [thread overview]
Message-ID: <d06193c1-eb84-f27d-cebf-7cde80b3d5ec@redhat.com> (raw)
In-Reply-To: <16cc6428-9a4c-87d0-f092-b7a21f64b0b8@redhat.com>
On 10/16/21 09:27, Paolo Bonzini wrote:
> On 16/10/21 04:04, Richard Henderson wrote:
>> I've seen a lot of failures on this job recently, and they're all
>> timeouts cloning the git submodules. Would it be better to mirror
>> these to gitlab?
>>
>
> They're not timeouts, they're issues with edk2's _own_ submodules.
>
> fatal: unable to access
> 'https://git.cryptomilk.org/projects/cmocka.git/': server certificate
> verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile:
> none
> fatal: clone of 'https://git.cryptomilk.org/projects/cmocka.git' into
> submodule path 'UnitTestFrameworkPkg/Library/CmockaLib/cmocka' failed
>
> roms/edk2 is already mirrored to gitlab, so we'd have to add mirrors for
> all of these and make edk2.yml configure the mirrors in .git/config. I
> think the edk2 project should do the mirroring instead...
IIUC QEMU EDK2 scripts don't require cmocka... IMHO (short term) we
should update the 'git submodule update' line in roms/Makefile.edk2
to only update the submodules we require.
next prev parent reply other threads:[~2021-10-17 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 2:04 gitlab build-edk2 failures Richard Henderson
2021-10-16 7:27 ` Paolo Bonzini
2021-10-17 14:58 ` Philippe Mathieu-Daudé [this message]
2021-10-18 5:23 ` Gerd Hoffmann
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=d06193c1-eb84-f27d-cebf-7cde80b3d5ec@redhat.com \
--to=philmd@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).