From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Build bug] Problem checking out submodules
Date: Tue, 01 Oct 2013 17:39:08 -0300 [thread overview]
Message-ID: <524B32EC.7000905@redhat.com> (raw)
In-Reply-To: <87ob78epls.fsf@linaro.org>
On 10/01/2013 04:52 PM, Alex Bennée wrote:
>
> 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.
That's an internal autotest test grid. Once a day we check the latest
qemu master and run sort of a smoke style test job, although it's not
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
and exec migration
5) Install a Windows 7 guest from an unattended XML, using the latest
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.
next prev parent reply other threads:[~2013-10-01 20:39 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
2013-10-01 20:39 ` Lucas Meneghel Rodrigues [this message]
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=524B32EC.7000905@redhat.com \
--to=lmr@redhat.com \
--cc=alex.bennee@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.