This is the initial support to test the Avocado features/options
using the Job API.
Signed-off-by: NWillian Rampazzo <willianr@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

This is waiting for #4062 to be solved.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Adding here some some possible use case of the current API. So far I
notice that we have two big cases: automatic job discovery vs
manual/custom job. I understand that there is room for improvements but
I would like to keep things consistent and intuitive here, because of
that this work is separating the logic behind the constructors and the
from_config() methods for both: Job() and TestSuite().
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

A lot of changes was made inside job and suite modules. This change will
update the docstrings to map with the current code.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Before this patch directories are not being created properly because
uuid1 was not being called. Took the oportunity to replace to uuid4.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

With .get() we don't need this, since we have default values.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

This is a natural move since with this flexibility would be nice to have
test_parameters per test suite.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

If job.config is present when creating a test suite then we will extend
this configuration. This will make it possible to passa a very long job
config and only small/specific configs for each test suite with the
changes.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests is not used
anymore, use https://gitlab.com/kvm-unit-tests/kvm-unit-tests instead.
Signed-off-by: NYihuang Yu <yihyu@redhat.com>

Since we have one variant per suite now, this plugin needs to get the
list of variants instead of only one.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Now variants is for each Test Suite, we should log from there. Also
jobdata.record only needs the job object pointer.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Since that we are going to a more decoupled way, users should create
they test suites using TestSuite() class.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

This will return a sum of all len(test_suite.tests) of the current job.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

This property will hold a list of TestSuite objects. I'm adding a
test_suite property here for backward compatibility. But it will be
removed soon.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

This is the final option that had to be converted from the older
standard of on/off, to a built in default and an option to either
enable or disable it.

So now the warning message can be removed completely.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

One small limitation introduced here is noted in the documentation,
that is, there's no longer a command line option to force the failfast
to the disabled during a replayed job, assuming the source job had
failfast enabled in the first place.

I believe removing this corner case is OK, given that the `avocado run
--replay` command is to be substituted in the very near future with a
`avocado replay` command, and the Job API should allow jobs to be
written for such corner cases.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

When ommitting '--sysinfo', the default will be applied, that is, it
will be enabled.  Users can now pass '--disable-sysinfo' on the
command line to disable sysinfo collection.

Also, remove the warning message about the future, now present,
change.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

utils.cpu.get_version: Fix IndexError: list index out of range

This method could be useful for other modules and since that is not
related to the job, IMO, makes sense to move to a more generic module.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Fixes:https://github.com/avocado-framework/avocado/issues/4067Signed-off-by: NYanan Fu <yfu@redhat.com>

That is, for the options that override the source job configuration.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

docs: Update contributor guide to include the new settings registration

make html was complaining about this invalid syntax
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

make html was complaining about invalid syntax.
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

lgtm: removed unused variable to make lgtm happy

This will fix #4040
Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Signed-off-by: NBeraldo Leal <bleal@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

The only reason for the "avocado/core/nrunner.py" to be standalone is
to ease its deployment into an environment that contains nothing but
Python itself.  This will hopefully change in the future when we solve
the deployment problem.

For now, it's clear that at least the StatusServer does not need to
live in that module and be deployed when tests are executed in a
different environment.  The StatusServer is used solely by the
`avocado nrun` command, and thus, can live on another module.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

To make sure that all interface checks, current and future, will be
run with all the existing runner implementations.

Reference: https://github.com/avocado-framework/avocado/issues/4058Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>