[Avocado-devel] [Virt-test-devel] [ANNOUNCEMENT] avocado-vt and virt-test merged

[Suqin Huang]

Hi Lucas,

Failed to load virt_test module.

# avocado run /bin/true
Error loading avocado.core.plugins.virt_test_list -> ImportError No module named virttest.standalone_test
Error loading avocado.core.plugins.virt_test -> ImportError No module named autotest.client
JOB ID     : c857e8d1e54bbd34a0c37f439444ef801d7a0c7d
JOB LOG    : /root/avocado/job-results/job-2015-08-04T16.29-c857e8d/job.log
JOB HTML   : /root/avocado/job-results/job-2015-08-04T16.29-c857e8d/html/results.html
TESTS      : 1
(1/1) /bin/true: PASS (0.00 s)
RESULTS    : PASS 1 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0
TIME       : 0.00 s


# avocado plugins

Unloadable plugin modules:
    avocado.core.plugins.virt_test       ImportError No module named autotest.client
    avocado.core.plugins.virt_test_list  ImportError No module named virttest.standalone_test


----- Original Message -----
> From: "Lucas Meneghel Rodrigues" <lmr at redhat.com>
> To: avocado-devel at redhat.com, "Virt Test Development Mailing List" <virt-test-devel at redhat.com>
> Cc: "Andrei Stepanov" <astepano at redhat.com>, "Ademar Reis" <areis at redhat.com>
> Sent: Tuesday, August 4, 2015 10:40:45 AM
> Subject: [Virt-test-devel] [ANNOUNCEMENT] avocado-vt and virt-test merged
> 
> Hello everyone:
> 
> After a lot of work and many reviews later, we have virt-test and
> avocado-vt merged:
> 
> https://github.com/avocado-framework/avocado-vt/commit/20dd39ef00db712f78419f07b10b8f8edbd19942
> 
> 
> What was done there?
> 
> * The virttest library calls to autotest APIs were converted to
> equivalent avocado API calls. There's still a tiny bit of autotest
> dependencies there to ensure correct test reporting
> * The project was adapted to be installable system-wide, through the
> means of distro packages, such as RPM. By default, the user files are
> all created in ~/avocado/data/avocado-vt (the ~/avocado location is
> configurable).
> * Avocado 0.27.0 and Avocado VT 0.27.0 were released, and both are
> available in our COPR repo so you can install them at your leisure.
> 
> 
> What does this mean from now on?
> 
> It officially means that virt-test is now avocado-vt, and that new
> development should be done in the avocado-vt repo. virt-test's repo is
> supposed to be left where it is, but we'll disable commit access to it.
> Our current virt-test maintainers will be granted access to the
> avocado-vt's repo, and we'll work to help our contributors to rebase
> their PRs against avocado-vt.
> 
> 
> Future
> 
> * The next step is to port our test providers to use avocado libraries,
> instead of the autotest ones, and move the repos location to avocado.
> * avocado-vt and our test providers will be maintained normally from
> this point forward.
> * Myself and my team will eventually move to focus on avocado-virt, the
> successor to avocado-vt. This is still ways to go before it can be
> considered ready for production (stability and feature set good enough
> for daily virt testing).
> * Somewhere down the line, avocado-vt will be in maintenance mode, and
> avocado-virt should be the focus of development.
> 
> We ask our awesome contributor and maintainer's patience while we work
> out eventual issues that came with the transition. We'd love to hear
> your criticisms and bug reports, and will work as quickly as we can to
> solve these issues.
> 
> 
> Notes
> 
> * Please add my COPR repo:
> 
> https://copr.fedoraproject.org/coprs/lmr/Autotest/
> 
> Check there for install instructions. To test avocado-vt, you can
> follow:
> 
> http://avocado-vt.readthedocs.org/en/latest/GetStartedGuide.html
> 
> That should do the trick. Any problems, please report them on:
> 
> https://github.com/avocado-framework/avocado-vt/issues/new
> 
> 
> Cheers!
> 
> 
> Lucas
> 
> _______________________________________________
> Virt-test-devel mailing list
> Virt-test-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/virt-test-devel
>