Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

That explains the dir structure for avocado test results.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Take system info in more opportunities:

1) Start job
2) End job
3) Start test
4) End test
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Add test linuxbuild (build Linux kernel)

Test subprocess improvements

Since we are using signals as a form of IPC (inter process
communication), let's use SIGUSR1, which is a user defined
signal that won't be easily mistaken with the more common
SIGTERM, that can be issued far more commonly.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NRuda Moura <rmoura@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

avocado.utils.archive: preserve permissions. when extracting.

Preserve file permissions when extracting data from tarballs,
so in some tests we have we don't need to set permissions too.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

Multiple output plugins

Some brief documentation on the JSON output plugin and
multiple output plugins.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

This way, tests in vm that fail won't trigger a problem
on XML outputs and crash avocado.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

As it was missing, causing an error with the json output.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

As I realized we did not have the journal plugin out here.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Add extra tests that verify that the always on output
plugins (JSON and Xunit inside the debug dir) are being
correctly generated and the outputs are valid.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

As specified in the requirements meeting, always have Xunit and
JSON outputs written to the results dir. The basic idea is to
enable any output plugins specified in the cmd line, the Xunit
and JSON compulsorily, and in the end, if there are no output
plugins requested in the command line, enable human output.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

It's necessary if we're generating valid outputs in
the appropriate places, and that they respect the
rules established so far.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

With the new attributes, change the output setup procedure
to verify if more than one output plugin wants to use the
stdout, in which case we print an error message and fail.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In order to be able to tell whether there's more than one
output plugin trying to use the stdout, add the 'output'
and 'output_option' attributes. This changes the current
output plugins to use and set these attributes correctly.

Fix the xunit unittest to take into account the new
attribute names.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Set up the TestResultProxy for the Job object, and
populate the test result objects according to what
the currently active plugins set. This means we go
on finding arguments with the suffix _result and
selecting any values that are classes derived from
TestResult and appending them to the result proxy.

With this, we can use any number of test result
plugins we'd like. If no test result objects are
set by plugins, fall back to the human output plugin.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Create a class that has the same interface as a
test result, but in fact has a list of test result
objects and can write to each of them any time
a test result operation is called. This is the
first step to make multiple output plugins to
work.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Virt off if remote off

Log message if remote or virt module is off.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

Signed-off-by: NRuda Moura <rmoura@redhat.com>

Test execution isolation using subprocesses and timeout feature

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Add a timeout test module for avocado, to exercise the
test timeout functionality. This test is supposed to
fail by timeout.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In order to ensure avocado tests won't mess with the
main avocado process' environment, execute them in
forked subprocesses. If the test params have a
'timeout' attribute, use it as the timeout param
of the .join() multiprocess method, allowing the
subprocesses to be killed after timeout seconds if
they did not complete.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In order to serialize the CmdError class, we need to
allow passing None command and CmdResult objects to
the class constructor.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In order to make the Test class serializable, implement
__getstate__ in a way that only exports the pickleable
attributes. This will be necessary for the following
patches that will insulate individual test executions
in forked processes.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Intended to be used in the special case a test times out.
Also, explain better what a TestError is supposed to be
(right now the description causes confusion).
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

avocado.utils: Small unused variable fixes

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

avocado.utils.remote: Add conenction timeout and attempts and remote_capable

Messages

We should use the absolute path when transfering the
file from the vm, and the basename only when assembling
the local path.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>