Introduce avocado.utils.script module to handle the creation
of scripts stored in the file system.

The module includes a flexible class for creating generic scripts and
 includes utilities functions too. Some examples:

    CONTENT = """
    #!/bin/sh
    echo "Hi There!"
    """

    x = avocado.utils.script.Script('/var/tmp/test.sh', CONTENT)
    x.save()
    ... do something with x, like run it ...
    x.remove()

    t = avocado.utils.script.make_temp_script('test.sh', CONTENT)
    ... do something with y, like run it ...

Avocado functional tests makes use of script creation,
so we will handle these creation using this proper module.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

avocado.job: Move sysinfo collection to test result object

We found a bug: The sysinfo collection was overwriting the
post information in jobs run through the vm plugin. Fix
the problem by moving the information collection to the
test result object. This is transparent to plugins, one
important requirement of the solution.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

avocado: Bump release to 0.14.0

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

examples: Be didactic with mux-environment.yaml.

avocado.core.tree: Match whole key in filters.

When filtering nodes, use the whole key for comparing.

So if you have /long and /longest and you're filtering for /long,
then it will match /long alone.

The previous behaviour was using the partial
string match, so both /long and /longest were being returned,
which is wrong.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

The example for multiplex must be didactic, using one
that would make sense in a real world usage.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

examples/mux-environmentyaml: Don't use local filters.

Remove lines that contains local filters, which is a feature
that is disabled by now (it's broken).
Signed-off-by: NRudá Moura <rmoura@redhat.com>

GDB stdout support

Manpage: Update information regarding global filters and multiplexer.

avocado.utils.remote: Changes to the .run() method

Avocado's GDB support when using avocado.utils.process API
now properly populates the command result stdout attribute.

This now allows tests that run programs and check its output
(stdout only, not stderr) to work transparently under GDB.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The init method on SubProcess got new parameters. Even if not
implemented in GDBSubProcess, those two ducks must quack alike.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Update the manual page of avocado to match the current status of the multiplexer,
regarding command line options for global filters.

Fix information on command line option -c | --content. It's about variables.

Plus:  cosmetic fixes around.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

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>

For convenience, save the contents of the whiteboard
into a file 'whiteboard', inside the test results.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Make the run() method to return a CmdResult object,
to make it symmetrical to the process.run() result.
Also, turn on logging of outputs for commands executed
on remote connections.

The reason why we want to do that is to increase the
debugging output we have for commands executed over
the fabric SSH connections. This way we can obtain
better, richer outputs in test logs that use our
fabric wrappers.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Sprint 14 pendencies

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

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

Basically, trying to encode information of the variants themselves
in the tag name is a lost battle, since:

1) We need unique test ids, and sometimes only the last part of
   the name of each variant combined is not going to cut it
2) Coding the entire path of each variant combined would create
   in many cases enormous tags and the point would be lost

So go back and use sequential numbers that match the output
of the multiplex plugin. This way it'll be easy to correlate
variants and tag numbers.
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>

Multiplex refinements: filters

In the current state of the code, the local filters are broken, so it's
better to keep it disable for now.

When getting leaves, if the node is root and alone, ignore it.
This situation is possible if filtering just preserves the root node,
so the root node will be leaf and returned.

That makes things a bit weird to get the variants,
because it will become one. So, we are going to ignore it.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Introduce function apply_filters(), which will prune
the tree that we use to multiplex and create variants,
by using rules for filter only and filter out, passed by
the command line (aka global filters).

It works for the test runner and for the multiplex plugin,
or anything that uses the TreeNode data structure with filters.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Adopt function path_parent() from the module avocado.multiplexer.
We will need this when we move the filtering to the level of
the tree.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Add method to detach a node from the tree.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Expand the list comprehension that handles filtering.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Tidy up options

So that we won't need to use sequential numbers in
multiplexed tests anymore.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

It was an option that didn't work properly, and made
more sense to the run subcommand anyway. Now, you can
provide one of the valid logging levels in the python
logging level translated to a lowercase string
('debug', 'info', 'warning', 'error', 'critical') and
that will be the level used for the job log in both
disk and --show-job-log.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>