On Tue, Jul 31, 2012 at 5:40 PM, Chris Evich <[email protected]> wrote: > On 07/30/2012 06:32 AM, Yu Mingfei wrote: >> >> Hi Chris, Lucas: >> >> According Lucas' advice, I add a parameter paused_after_start_vm >> to control paused state of domain. >> >> As options_ref, I have not thought up more suitable idea, >> so I will put it in my todolist.^_^ >> >> Yu Mingfei (4): >> virt.virt_env_process:add paused state of domain for preprocess_vm. >> virt.libvirt_vm:Add a function of virsh domname. >> virt.subtest.cfg.sample:Add testcases for virsh domname. >> client.tests.libvirt:Add test for virsh domname. >> >> client/tests/libvirt/tests/virsh_domname.py | 64 >> +++++++++++++++++++++++++++ >> client/virt/base.cfg.sample | 1 + >> client/virt/libvirt_vm.py | 10 ++++ >> client/virt/subtests.cfg.sample | 51 +++++++++++++++++++++ >> client/virt/virt_env_process.py | 3 + >> 5 files changed, 129 insertions(+), 0 deletions(-) >> create mode 100644 client/tests/libvirt/tests/virsh_domname.py >> >> > > Just FYI: I put in 1/4 into next, but am still planning to take closer look > at rest of patches. Unfortunately, my test box was complaining loudly. I > fixed it today only to find a autotest bug introduced in next that's > preventing me from running it :( Anyway, it's still at the top of my list > once I get things working.
I've fixed the python 2.4 illegal syntax bug and rebased next. Well, this week is being riddle with bugs. Good thing we're managing to fix them. -- Lucas _______________________________________________ Autotest-kernel mailing list [email protected] https://www.redhat.com/mailman/listinfo/autotest-kernel
