All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lukáš Doktor" <ldoktor@redhat.com>
To: lei yang <yanglei.fage@gmail.com>
Cc: autotest@test.kernel.org, kvm-autotest@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 3/4] [KVM-autotest] tests.cfg.sample: change import order
Date: Mon, 12 Mar 2012 09:11:15 +0100	[thread overview]
Message-ID: <4F5DAFA3.3030303@redhat.com> (raw)
In-Reply-To: <CAHsH0E-VgOYbF4PsUZtXZ71548fW4CSYaqrU=H2SgMQYo5ATDQ@mail.gmail.com>

Yes, as I mentioned before, I wanted to put subtests.cfg after the other 
imports, but it caused a lot of trouble. So I find another solution 
without changing the import order.

Dne 12.3.2012 08:49, lei yang napsal(a):
> On Mon, Mar 12, 2012 at 3:15 PM, Lukáš Doktor<ldoktor@redhat.com>  wrote:
>> Hi,
>>
>> it caused problems so I had to modify it a bit. It's already fixed and
>> applied in upstream.
>>
>
> You mean you want put "include subtests.cfg" on the top or in the end?
> from your idea you seems want it to be the end to change some
> parameter easily
>
> after I pull the tree,
>
> I got something like (git show 6e4b5cffe999714357116884fcc4eb27fae41260)
>
> include base.cfg
> include subtests.cfg
> include guest-os.cfg
> include guest-hw.cfg
> include cdkeys.cfg
> include virtio-win.cfg
>
> but I thought you may want to it be like
>
> include base.cfg
> include guest-os.cfg
> include guest-hw.cfg
> include cdkeys.cfg
> include virtio-win.cfg
> include subtests.cfg
>
> or I'm wrong?
>
>
>
>
>> Regards,
>> Lukáš
>>
>> Dne 12.3.2012 04:34, lei yang napsal(a):
>>
>>> Howerver, you did the opposite thing or you did it two times
>>>
>>> commit 6e4b5cffe999714357116884fcc4eb27fae41260
>>> Author: Lucas Meneghel Rodrigues<lmr@redhat.com>
>>> Date:   Wed Feb 29 18:47:14 2012 -0300
>>>
>>>      Revert "tests.cfg.sample: change import order"
>>>
>>>      This reverts commit e64b17d7a15602db0cd26ec55ccc902010985d0c,
>>>      as it's causing problems with the test execution order.
>>>
>>>      Signed-off-by: Lucas Meneghel Rodrigues
>>>
>>> diff --git a/client/tests/kvm/tests-shared.cfg.sample
>>> b/client/tests/kvm/tests-shared.cfg.sample
>>> index bda982d..c6304b3 100644
>>> --- a/client/tests/kvm/tests-shared.cfg.sample
>>> +++ b/client/tests/kvm/tests-shared.cfg.sample
>>> @@ -5,11 +5,11 @@
>>>
>>>   # Include the base config files.
>>>   include base.cfg
>>> +include subtests.cfg
>>>   include guest-os.cfg
>>>   include guest-hw.cfg
>>>   include cdkeys.cfg
>>>   include virtio-win.cfg
>>> -include subtests.cfg
>>>
>>>   # Virtualization type (kvm or libvirt)
>>>   vm_type = kvm
>>>
>>>
>>> Lei
>>>
>>>
>>> On Tue, Feb 28, 2012 at 2:42 AM, Lukas Doktor<ldoktor@redhat.com>    wrote:
>>>> Currently subtests.cfg is proceeded and then all other configs. My test
>>>> needs to override smp parameter in some variant which is currently
>>>> impossible.
>>>>
>>>> Using words current order means: we define subtests variants, than we
>>>> specify base and guest and other details. In the end we limit what
>>>> we want to execute.
>>>>
>>>> My proposed order enables forcing base/guest params in subtest variants.
>>>>
>>>> By words this means we specify base, guest system, cdkeys, etc. and in
>>>> the end we define subtests with various variants. Then we limit what
>>>> we actually want to execute but now subtest can force varius base/guest
>>>> settings.
>>>>
>>>> Signed-off-by: Lukas Doktor<ldoktor@redhat.com>
>>>> ---
>>>>   client/tests/kvm/tests-shared.cfg.sample |    2 +-
>>>>   1 files changed, 1 insertions(+), 1 deletions(-)
>>>>
>>>> diff --git a/client/tests/kvm/tests-shared.cfg.sample
>>>> b/client/tests/kvm/tests-shared.cfg.sample
>>>> index c6304b3..bda982d 100644
>>>> --- a/client/tests/kvm/tests-shared.cfg.sample
>>>> +++ b/client/tests/kvm/tests-shared.cfg.sample
>>>> @@ -5,11 +5,11 @@
>>>>
>>>>   # Include the base config files.
>>>>   include base.cfg
>>>> -include subtests.cfg
>>>>   include guest-os.cfg
>>>>   include guest-hw.cfg
>>>>   include cdkeys.cfg
>>>>   include virtio-win.cfg
>>>> +include subtests.cfg
>>>>
>>>>   # Virtualization type (kvm or libvirt)
>>>>   vm_type = kvm
>>>> --
>>>> 1.7.7.6
>>>>
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>

_______________________________________________
Autotest mailing list
Autotest@test.kernel.org
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest

  reply	other threads:[~2012-03-12  8:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 18:42 [KVM-autotest] Cgroup-kvm rework Lukas Doktor
2012-02-27 18:42 ` [PATCH 1/4] [KVM-autotest] virt.kvm_vm: Make snapshot and boot params optional Lukas Doktor
2012-02-27 18:42 ` [PATCH 2/4] [KVM-autotest] virt.virt_vm: Add option to create raw images with dd Lukas Doktor
2012-02-27 18:42 ` [PATCH 3/4] [KVM-autotest] tests.cfg.sample: change import order Lukas Doktor
2012-03-12  3:34   ` lei yang
2012-03-12  7:15     ` Lukáš Doktor
2012-03-12  7:49       ` lei yang
2012-03-12  8:11         ` Lukáš Doktor [this message]
2012-02-27 18:42 ` [PATCH 4/4] [KVM-autotest] tests.cgroup: Rework test execution Lukas Doktor
2012-02-28 19:07 ` [KVM-AUTOTEST] [KVM-autotest] Cgroup-kvm rework 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=4F5DAFA3.3030303@redhat.com \
    --to=ldoktor@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm-autotest@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=yanglei.fage@gmail.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.