From: "Alex Bennée" <alex.bennee@linaro.org>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Build bug] Problem checking out submodules
Date: Tue, 01 Oct 2013 20:52:25 +0100 [thread overview]
Message-ID: <87ob78epls.fsf@linaro.org> (raw)
In-Reply-To: <524B261C.3070400@redhat.com>
lmr@redhat.com writes:
> On 10/01/2013 04:37 PM, Alex Bennée wrote:
>>
>> lmr@redhat.com writes:
>>
>>> Hello:
>>>
>>> In the daily qemu.git autotest run, I started to see the following
>>> problem while checking out the qemu.git tree and checking out the
>>> submodules:
Oh I just noticed that. Is this Stefan's buildbot stuff or an internal
auto-test set-up? I only ask because I noticed this while testing my
Travis patches. I'm trying to get a feel for what CI type tasks are
running in QEMU world, both public and internal to companies.
>>
>> It looks like a recent commit to update the version of SeaBIOS used
>> broke the build as the qemu mirror hasn't been updated yet. You can work
>> around it for now by patching .gitmodules:
>
> Ok, thanks for the explanation. Local patching is not really a scalable
> option when performing automated testing though. I'll keep the daily job
> running, and when the mirror is updated, the failures will stop.
I'll be submitting a patch tomorrow when I post the next version of the
Travis patches up to the mailing list.
--
Alex Bennée
next prev parent reply other threads:[~2013-10-01 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 18:12 [Qemu-devel] [Build bug] Problem checking out submodules Lucas Meneghel Rodrigues
2013-10-01 19:37 ` Alex Bennée
2013-10-01 19:44 ` Lucas Meneghel Rodrigues
2013-10-01 19:52 ` Alex Bennée [this message]
2013-10-01 20:39 ` Lucas Meneghel Rodrigues
2013-10-02 1:32 ` Anthony Liguori
2013-10-02 3:47 ` Lucas Meneghel Rodrigues
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=87ob78epls.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=lmr@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).