From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/kvm-unit-tests: new package
Date: Wed, 21 Sep 2016 09:24:49 +0200 [thread overview]
Message-ID: <20160921092449.32147532@free-electrons.com> (raw)
In-Reply-To: <20160817230236.8255-1-cyrilbur@gmail.com>
Hello,
On Thu, 18 Aug 2016 09:02:36 +1000, Cyril Bur wrote:
> The unit tests are tiny guest operating systems that generally execute
> only tens of lines of C and assembler test code in order to obtain its
> PASS/FAIL result. Unit tests provide KVM and virt hardware functional
> testing by targeting the features through minimal implementations of
> their use per the hardware specification. The simplicity of unit tests
> make them easy to verify they are correct, easy to maintain, and easy
> to use in timing measurements. Unit tests are also often used for
> quick and dirty bug reproducers. The reproducers may then be kept as
> regression tests. It's strongly encouraged that patches implementing
> new KVM features are submitted with accompanying unit tests.
> http://www.linux-kvm.org/page/KVM-unit-tests
>
> Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
This package is causing a good number of build failures. See:
arm | kvm-unit-tests-682187afcc99... | NOK | http://autobuild.buildroot.net/results/a81d40f1453ee027c7e2a9da01f482e1d09b464d
i686 | kvm-unit-tests-682187afcc99... | NOK | http://autobuild.buildroot.net/results/20efe1e310fe71a587774bbe8490d6357acc8edd
x86_64 | kvm-unit-tests-682187afcc99... | NOK | http://autobuild.buildroot.net/results/07deb6183ed23447de5182ee20df6c9c49e5ca49
Could you have a look and provide patches to address these?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-21 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 23:02 [Buildroot] [PATCH] package/kvm-unit-tests: new package Cyril Bur
2016-09-19 14:48 ` Thomas Petazzoni
2016-09-19 21:07 ` Peter Korsgaard
2016-09-19 23:12 ` Cyril Bur
2016-09-21 7:24 ` Thomas Petazzoni [this message]
2016-09-22 0:01 ` Cyril Bur
2016-09-22 5:18 ` Peter Korsgaard
2016-09-22 9:34 ` Thomas Petazzoni
2016-09-22 9:42 ` Peter Korsgaard
2016-09-23 6:06 ` Cyril Bur
2016-09-23 6:12 ` Thomas Petazzoni
2016-09-23 6:14 ` Cyril Bur
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=20160921092449.32147532@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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