All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uri Lublin <uril@redhat.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: KVM mailing list <kvm@vger.kernel.org>,
	Autotest mailing list <autotest@test.kernel.org>,
	Dror Russo <drusso@redhat.com>
Subject: Re: [Autotest] [PATCH] Adding kvm test (kvm autotest upstream merge proposal take 2)
Date: Mon, 01 Jun 2009 17:00:05 +0300	[thread overview]
Message-ID: <4A23DEE5.4060309@redhat.com> (raw)
In-Reply-To: <1243797888.2837.28.camel@localhost.localdomain>

On 05/31/2009 10:24 PM, Lucas Meneghel Rodrigues wrote:
> The test was just commited. Stage 1 of the upstream merge complete.
>
> Please let me know if you have any doubts. Happy hacking!

Please credit Dror Russo for his contribution (see below).
Dror has been contributing since kvm-autotest early days.

Thanks,
     Uri.

>
> On Fri, 2009-05-29 at 14:58 -0300, Lucas Meneghel Rodrigues wrote:
>> After some conversations, we decided to rename kvm_runtest_2 to kvm.
>> Also, corrected some small mistakes I've done on the first patches.
>>
>> Hopefully, things are good to go. From the feedback I've got on the IRC
>> channel, people are happy with the current state of the test. I am going
>> to commit it if nobody pronounces against it :)
>>
>> From: Uri Lublin (uril@redhat.com)

           Dror Russo (drusso@redhat.com)

>>        Michael Goldish (mgoldish@redhat.com)
>>        David Huff (dhuff@redhat.com)
>>        Alexey Eromenko (aeromenk@redhat.com)
>>        Mike Burns (mburns@redhat.com)
>>
>> Signed-off-by: Lucas Meneghel Rodrigues<lmr@redhat.com>
>>
>> Index: trunk/client/tests/kvm/control
>> ===================================================================
>> --- trunk/client/tests/kvm/control	(revision 0)
>> +++ trunk/client/tests/kvm/control	(revision 0)
>> @@ -0,0 +1,155 @@
>> +AUTHOR = """
>> +uril@redhat.com (Uri Lublin)

    +drusso@redhat.com (Dror Russo)

>> +mgoldish@redhat.com (Michael Goldish)
>> +dhuff@redhat.com (David Huff)
>> +aeromenk@redhat.com (Alexey Eromenko)
>> +mburns@redhat.com (Mike Burns)
>> +"""



>> Index: trunk/client/tests/kvm/make_html_report.py
>> ===================================================================
>> --- trunk/client/tests/kvm/make_html_report.py	(revision 0)
>> +++ trunk/client/tests/kvm/make_html_report.py	(revision 0)
>> @@ -0,0 +1,1735 @@
>> +#!/usr/bin/python
>> +"""
>> +Script used to parse the test results and generate an HTML report.
>> +
>> +@copyright: (c)2005-2007 Matt Kruse (javascripttoolbox.com)
>> +@copyright: Red Hat 2008-2009

    +@author: drusso@redhat.com (Dror Russo)

>>
>> Index: trunk/client/tests/kvm/kvm.py
>> ===================================================================
>> --- trunk/client/tests/kvm/kvm.py	(revision 0)
>> +++ trunk/client/tests/kvm/kvm.py	(revision 0)
>> @@ -0,0 +1,109 @@
>> +import sys, os, time, shelve, random, resource, logging
>> +from autotest_lib.client.bin import test
>> +from autotest_lib.client.common_lib import error
>> +
>> +
>> +class test_routine:
>> +    def __init__(self, module_name, routine_name):
>> +        self.module_name = module_name
>> +        self.routine_name = routine_name
>> +        self.routine = None
>> +
>> +
>> +class kvm(test.test):
>> +    """
>> +    Suite of KVM virtualization functional tests.
>> +    Contains tests for testing both KVM kernel code and userspace code.
>> +
>> +    @copyright: Red Hat 2008-2009
>> +    @author: Uri Lublin (uril@redhat.com)

    +    @author: Dror Russo (drusso@redhat.com)

>> +    @author: Michael Goldish (mgoldish@redhat.com)
>> +    @author: David Huff (dhuff@redhat.com)
>> +    @author: Alexey Eromenko (aeromenk@redhat.com)
>> +    @author: Mike Burns (mburns@redhat.com)
>> +    """


           reply	other threads:[~2009-06-01 14:00 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1243797888.2837.28.camel@localhost.localdomain>]

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=4A23DEE5.4060309@redhat.com \
    --to=uril@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=drusso@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@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 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.