All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] test/docker/Makefile.include: add a generic docker-run target
Date: Wed, 21 Sep 2016 11:22:35 +0100	[thread overview]
Message-ID: <87h999blhw.fsf@linaro.org> (raw)
In-Reply-To: <20160921100942.GA31288@lemon>


Fam Zheng <famz@redhat.com> writes:

> On Wed, 09/21 10:44, Alex Bennée wrote:
>>
>> FWIW we already have some coverage of the MacOSX builds via Travis
>> (although being able to run it quickly on a dev system would be useful).
>
> Being able to detect breakage earlier than a pull req bounce from Peter would
> also be good.

True. Although more people have started enabling Travis on their private
git trees, we just don't see it as much as IRC doesn't get spammed for
anything other than runs against the official tree.

>
>>
>> >
>> > I haven't prioritied debootstrap for now, because arm is not too different than
>> > x86 in terms of endianness and stuff, and qemu-user is probably much slower
>> > than native compilers.
>>
>> It is much slower although qemu-user can at least take advantage of all
>> those extra cores on your server ;-)
>>
>> 32 bit builds are also an area that needs good coverage as I'm pretty
>> sure most devs have only x86_64 boxes these days.
>
> Yes, test-mingw has it.

Ahh cool :-)

--
Alex Bennée

      reply	other threads:[~2016-09-21 10:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 13:56 [Qemu-devel] [RFC] test/docker/Makefile.include: add a generic docker-run target Alex Bennée
2016-09-21  4:09 ` Fam Zheng
2016-09-21  7:50   ` Alex Bennée
2016-09-21  8:10     ` Fam Zheng
2016-09-21  9:44       ` Alex Bennée
2016-09-21 10:09         ` Fam Zheng
2016-09-21 10:22           ` Alex Bennée [this message]

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=87h999blhw.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=famz@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 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.