From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34789)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <alex.bennee@linaro.org>) id 1VR5zl-00075h-Nn
	for qemu-devel@nongnu.org; Tue, 01 Oct 2013 15:52:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <alex.bennee@linaro.org>) id 1VR5zf-0000bi-P2
	for qemu-devel@nongnu.org; Tue, 01 Oct 2013 15:52:33 -0400
Received: from static.88-198-71-155.clients.your-server.de
	([88.198.71.155]:54852 helo=socrates.bennee.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <alex.bennee@linaro.org>) id 1VR5zf-0000bZ-J4
	for qemu-devel@nongnu.org; Tue, 01 Oct 2013 15:52:27 -0400
References: <524B1083.3080807@redhat.com> <874n906avo.fsf@linaro.org>
	<524B261C.3070400@redhat.com>
From: Alex =?utf-8?Q?Benn=C3=A9e?= <alex.bennee@linaro.org>
Message-ID: <87ob78epls.fsf@linaro.org>
In-reply-to: <524B261C.3070400@redhat.com>
Date: Tue, 01 Oct 2013 20:52:25 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [Qemu-devel] [Build bug] Problem checking out submodules
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>


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