On Wed, Aug 5, 2015 at 6:03 AM xutian <[email protected]> wrote: > Hi Lucas, > > Below is some feedback for avocado-vt-plugin base on my testing with > latest released avocado-vt-plugin RPM package. > > 1. It's better to print formatted trace-back like autotest does when > exception raise at load avocado-vt-plugin, it will very helpful to do > bug fix. > like below exception, > Test discovery plugin > <avocado.core.plugins.virt_test.VirtTestLoader object at 0x23e5390> > failed: 'Namespace' object has no attribute 'netdst' > Above exception raise but not trace-back print, it's hard to know > where this exception is thrown for a new user.(Most of team member in > our team is new user now) >
We can revert it back to printing the traceback, during the development phase we were printing it but after a lot of testing, we came back to suppressing it. It could be even a config option to enable/disable it. > 2. vt_nettype in avocado-virt-0.27.0-1.el7.centos.noarch can't be pass > to virt_test plugin from virt-test.conf because exception mentioned in > item 1. > It caused by a typo in process options function and it has be fixed > in upstream master but not include in latest released RPM. > I could do a minor release with the bugs fixed so far. Our full attention is dedicated to the bug fixes. The question is whether the official release can be delayed until we amass a larger number of fixes, and you could build rpms straight from master using 'make build-rpm-all' meanwhile. > 3. I suggest to use a stable code to do release, make RPM packages. And > each release should have details release notes and detail change log for > relased RPM packages. > We did do a lot of testing when developing avocado-vt, but clearly there are lots of different use cases and we couldn't cover them all. That's why your testing is so valuable. Believe me, I'd love to ship perfectly stable code on this first attempt, but well, that didn't really pan out. As for the release notes and detailed change log, we'll do our best. > 4. vt-config option works but customized configuration can't update > default configuration from virt-test.conf, which break my test becase > test VM is not the expect VM. > I just saw your bug and will work on it as quickly as possible. > And I will continue my testing and provider feedback to you. > Thanks. Sorry for the bugs found, and thanks for all the feedback!
_______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
