public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Cole Robinson <crobinso@redhat.com>
To: kvm@vger.kernel.org
Cc: kwolf@redhat.com, Cole Robinson <crobinso@redhat.com>
Subject: [PATCH kvm-unit-tests v2 0/4] Have x86-run parse unittests.cfg
Date: Sun, 14 Apr 2013 14:18:30 -0400	[thread overview]
Message-ID: <cover.1365962962.git.crobinso@redhat.com> (raw)

First two patches are trivial bits. Rest rewrites x86-run in python,
which then makes it easy to parse unittests.cfg. This makes it
simpler to invoke individual unittests the same way autotest does.

Kevin has a similar series[1], but I'm reposting this for completeness.

[1] http://www.spinics.net/lists/kvm/msg89471.html

v2:
    Drop patch that removed x86/README
    Don't remove manual invocations examples from README

Cole Robinson (4):
  .gitignore: Add *.flat and config.mak
  x86/run-kvm-unit-tests: Drop it
  Rewrite x86-run in python
  x86-run: Pull extra arguments from unittests.cfg

 .gitignore             |   2 +
 README                 |  14 ++++--
 x86-run                | 133 +++++++++++++++++++++++++++++++++++++++----------
 x86/run-kvm-unit-tests |   6 ---
 4 files changed, 117 insertions(+), 38 deletions(-)
 delete mode 100644 x86/run-kvm-unit-tests

-- 
1.8.1.4


             reply	other threads:[~2013-04-14 18:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 18:18 Cole Robinson [this message]
2013-04-14 18:18 ` [PATCH kvm-unit-tests v2 1/4] .gitignore: Add *.flat and config.mak Cole Robinson
2013-04-14 18:18 ` [PATCH kvm-unit-tests v2 2/4] x86/run-kvm-unit-tests: Drop it Cole Robinson
2013-04-14 18:18 ` [PATCH kvm-unit-tests v2 3/4] Rewrite x86-run in python Cole Robinson
2013-04-14 18:18 ` [PATCH kvm-unit-tests v2 4/4] x86-run: Pull extra arguments from unittests.cfg Cole Robinson
2013-04-15  8:30 ` [PATCH kvm-unit-tests v2 0/4] Have x86-run parse unittests.cfg Kevin Wolf
2013-04-15 10:47   ` Paolo Bonzini
2013-04-15 13:40     ` Cole Robinson

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=cover.1365962962.git.crobinso@redhat.com \
    --to=crobinso@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    /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