From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43699) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR6j2-0000cI-FQ for qemu-devel@nongnu.org; Tue, 01 Oct 2013 16:39:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VR6iw-0006dF-Ez for qemu-devel@nongnu.org; Tue, 01 Oct 2013 16:39:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41717) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR6iw-0006dB-7C for qemu-devel@nongnu.org; Tue, 01 Oct 2013 16:39:14 -0400 Message-ID: <524B32EC.7000905@redhat.com> Date: Tue, 01 Oct 2013 17:39:08 -0300 From: Lucas Meneghel Rodrigues MIME-Version: 1.0 References: <524B1083.3080807@redhat.com> <874n906avo.fsf@linaro.org> <524B261C.3070400@redhat.com> <87ob78epls.fsf@linaro.org> In-Reply-To: <87ob78epls.fsf@linaro.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [Build bug] Problem checking out submodules List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?QWxleCBCZW5uw6ll?= Cc: qemu-devel On 10/01/2013 04:52 PM, Alex Benn=C3=A9e wrote: > > lmr@redhat.com writes: > >> On 10/01/2013 04:37 PM, Alex Benn=C3=A9e 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. That's an internal autotest test grid. Once a day we check the latest=20 qemu master and run sort of a smoke style test job, although it's not=20 so, 'smoky', since it takes about a couple of hours to run. Tests covered= : 1) Installing Fedora 19 on a host 2) git clone the latest master 3) Install a RHEL 6.4 guest from kickstart 4) Basic boot, reboot, single host migration using tcp, unix socket, fd=20 and exec migration 5) Install a Windows 7 guest from an unattended XML, using the latest=20 virtio drivers that our windows drivers team releases. 6) Perform the same tests outlined in 4) I hope it gives you a better idea of what's going on.