public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: autotest@test.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/4] Make possible to run client tests as subtests
Date: Tue, 24 May 2011 11:24:40 -0300	[thread overview]
Message-ID: <1306247082.2345.7.camel@freedom> (raw)
In-Reply-To: <1306220891-3993-1-git-send-email-lmr@redhat.com>

On Tue, 2011-05-24 at 04:08 -0300, Lucas Meneghel Rodrigues wrote:
> In order to avoid duplication of code, make it possible to run the
> existing autotest client tests as subtests. This patchset is result
> of work on Jiri Zupka original single patch, the differences:
> 
> * Removed example subtest KVM autotest test
> * Renamed some API introduced to net_utils for consistency
> * Rewrote netperf in terms of the new 'subtest' infrastructure

For the record of documentation, there are still some things bothering
me with this patchset:

* I still didn't check whether the changes to autotest core (test class)
do break unittests. We might want to write a unittest for the new
methods of the test class.
* Maybe rather than simply calling job.runtest() we would be better of
executing the subtest on a new thread?
* The netperf reimplementation clearly lacks the functionality of the
current implementation. We need more work on it.

I asked Jiri to pick the patchset and look at these points of
improvement.

> Lucas Meneghel Rodrigues (4):
>   client.bin.net.net_utils: Introduce get_local_ip()
>   client: Make it possible to run subtests in autotest
>   tools: Make html_report to deal with subtest results
>   KVM test: Rewrite netperf in terms of subtest
> 
>  client/bin/client_logging_config.py |    5 +-
>  client/bin/net/net_utils.py         |   17 +++++
>  client/common_lib/base_job.py       |    2 +
>  client/common_lib/logging_config.py |    3 +-
>  client/common_lib/test.py           |   21 ++++++-
>  client/tools/html_report.py         |  124 +++++++++++++++++++---------------
>  client/virt/tests/netperf.py        |  117 +++++++++------------------------
>  7 files changed, 143 insertions(+), 146 deletions(-)
> 



  parent reply	other threads:[~2011-05-24 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24  7:08 [PATCH 0/4] Make possible to run client tests as subtests Lucas Meneghel Rodrigues
2011-05-24  7:08 ` [PATCH 1/4] client.bin.net.net_utils: Introduce get_local_ip() Lucas Meneghel Rodrigues
2011-05-24  7:08 ` [PATCH 2/4] client: Make it possible to run subtests in autotest Lucas Meneghel Rodrigues
2011-05-24  7:08 ` [PATCH 3/4] tools: Make html_report to deal with subtest results Lucas Meneghel Rodrigues
2011-05-24  7:08 ` [PATCH 4/4] KVM test: Rewrite netperf in terms of subtest Lucas Meneghel Rodrigues
2011-05-24 14:24 ` Lucas Meneghel Rodrigues [this message]
2011-06-01 19:31 ` [PATCH 0/4] Make possible to run client tests as subtests 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=1306247082.2345.7.camel@freedom \
    --to=lmr@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox