From: Thomas Huth <thuth@redhat.com>
To: "Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] .travis.yml: Use travis_retry() in case of network issues
Date: Mon, 15 Jun 2020 07:12:22 +0200 [thread overview]
Message-ID: <bc9c331b-cfd4-9d46-3c02-86e95d93be88@redhat.com> (raw)
In-Reply-To: <5ba02176-34c9-f984-95f4-1f61103d785c@ilande.co.uk>
On 14/06/2020 11.48, Mark Cave-Ayland wrote:
> On 13/06/2020 14:06, Philippe Mathieu-Daudé wrote:
>
>> Use travis_retry() when cloning SLOF (see 31c8cc4f94e) in the
>> s390x container job, to avoid build failures:
>>
>> $ ( cd ${SRC_DIR} ; git submodule update --init roms/SLOF )
>> Submodule 'roms/SLOF' (https://git.qemu.org/git/SLOF.git) registered for path 'roms/SLOF'
>> Cloning into '/home/travis/build/user/qemu/roms/SLOF'...
>> fatal: unable to access 'https://git.qemu.org/git/SLOF.git/': Could not resolve host: git.qemu.org
>> fatal: clone of 'https://git.qemu.org/git/SLOF.git' into submodule path '/home/travis/build/user/qemu/roms/SLOF' failed
>> Failed to clone 'roms/SLOF'. Retry scheduled
>> Cloning into '/home/travis/build/user/qemu/roms/SLOF'...
>> fatal: unable to access 'https://git.qemu.org/git/SLOF.git/': Could not resolve host: git.qemu.org
>> fatal: clone of 'https://git.qemu.org/git/SLOF.git' into submodule path '/home/travis/build/user/qemu/roms/SLOF' failed
>> Failed to clone 'roms/SLOF' a second time, aborting
>> The command "( cd ${SRC_DIR} ; git submodule update --init roms/SLOF )" exited with 1.
>>
>> Reported-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> ---
>> .travis.yml | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/.travis.yml b/.travis.yml
>> index ec6367af1f..19a1b55aab 100644
>> --- a/.travis.yml
>> +++ b/.travis.yml
>> @@ -496,7 +496,7 @@ jobs:
>> - CONFIG="--disable-containers --target-list=${MAIN_SOFTMMU_TARGETS},s390x-linux-user"
>> - UNRELIABLE=true
>> script:
>> - - ( cd ${SRC_DIR} ; git submodule update --init roms/SLOF )
>> + - ( cd ${SRC_DIR} ; travis_retry git submodule update --init roms/SLOF )
>> - BUILD_RC=0 && make -j${JOBS} || BUILD_RC=$?
>> - |
>> if [ "$BUILD_RC" -eq 0 ] ; then
>
> Hi Phil,
>
> Thanks for diagnosing and proposing a fix. Is there a reason why SLOF in particular
> is failing compared to other repositories that might also need a similar change?
That's what I wonder, too. If git.qemu.org could not be resolved for
SLOF.git, why should it be resolvable for the other submodules that are
checked out automatically during the build process?
Thomas
next prev parent reply other threads:[~2020-06-15 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 13:06 [PATCH] .travis.yml: Use travis_retry() in case of network issues Philippe Mathieu-Daudé
2020-06-14 9:48 ` Mark Cave-Ayland
2020-06-15 5:12 ` Thomas Huth [this message]
2020-06-15 6:38 ` 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=bc9c331b-cfd4-9d46-3c02-86e95d93be88@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=philmd@redhat.com \
--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).