Since the 'config' plugin supersedes functionality
in the 'datadir' plugin, let's remove it from avocado.
Update the configuration accordingly.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Add a section that explains how the avocado config system
works.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Whatever is in the system wide settings can be later
overriden by users. Also, change the settings.config_path
attribute to settings.config_paths, and change it to
a list. This way users can see the order in which their
config files are parsed. Also, Introduce a system wide conf.d
directory, that is supposed to ship config files for avocado
plugins. The order for config parsing is:

 * System wide avocado config (/etc/avocado/avocado.conf)
 * System wide avocado plugins config (/etc/avocado/conf.d/*.conf)
 * Local config for the user running avocado (~/.config/avocado/avocado.conf)
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

To avoid problems with /tmp being mounted on a tmpfs in
certain systems.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Add the config plugin, that introduces the 'config'
subcommand. This shows to the user the config keys
available in the system.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

As discussed in the Trello card

https://trello.com/c/WsDMg7RP/161-initial-support-for-avocado-config-files-server-and-client

Move settings.ini to avocado.conf. The basic idea is
that the name is more intuitive.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

And put a reminder of the purpose of that file, while we're at it.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Fix garbage output on remote and vm plugins.

When using the remote or vm plugins, the JSON (or XML) result from
the remote server is coming with garbage at the end.
This commit fix this by filtering the result.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Move class TestRunner inside avocado.job into a proper new module avocado.runner

Change plugins vm and remote to use new module `avocado.runner`
that contains the TestRunner class.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Remove TestRunner class from this module, it's now defined inside new
module `avocado.runner`.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Creates the module `avocado.runner` where the `TestRunner` class lives.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

 Run avocado when called by 'python -m avocado'

selftests..multiplex_tests: Check that vars changes

Replace test_run_mplex_timeout with test_run_mplex_params test which
executes 'env_variables.sh' and checks that output contain correct
output. This test checks the multiplexer capability to change variable
value.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Add a main entry point when avocado is called
by the command line option 'python -m avocado'.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Plugin tweaks

Put the sysinfo and test_lister plugins into separate
plugin files. Although not strictly necessary, the
neat 1 plugin - 1 source file relation makes things
organized and easy to understand.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

This way we define more clearly the attributes of the
plugin object (many of them will implement a parser
object).
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Get to a more toned down output for the subcommands
'datadir', 'plugins' and 'list'.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

It is useful information to the user where the config file
is, to reinforce where avocado is picking the default values.
So add it to the output of `datadir` and `list` subcommands.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

multiprocessing.Queue().put() is asynchronous and in case the test died
critically before the put() was executed, TestRunner.run() waited for
infinity for early_state. This patch uses
multiprocessing.queues.SimpleQueue(), where it's guaranteed that after
executing put() the data are already in the SimpleQueue.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

avocado.test: Support params passing to DropinTests [v2]

This patch injects all params as env variables to
DropinTests. This is very useful for multiplexing
these tests.

Additionally the env_variables.sh example test was
adjusted to print CUSTOM_VARIABLE, which can be used
in selftest.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Make use of python-subprocess32 module if available.

Include wrappers script when creating `avocado-examples` package.

python-subprocess32 [https://code.google.com/p/python-subprocess32/]
is a backport of Python 3.2 subprocess module with:

* Better process forking.
* More reliable when running with threads.

Although we're not going to use any feature of subprocess32,
this change turn it possible to use subprocess32 as a drop-in
replacement for the original subprocess module.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Include all examples/wrappers/*.sh scripts when building
the `avocado-examples` package. The scripts will live under
`/usr/share/avocado/wrappers` when installed.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Fix rpmbuild

setuptools is not a standard module and makes things
unpredictable and forces us to push MANIFEST.in to
include more files so the binary distributions get
filled appropriately. In a retrospect, it was a bad
idea. Let's revert it.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Fix abort test taking too long to execute

It is likely that a race condition in avocado makes the abort
test to take a long while executing (24 hours), but that
was only identified in the Travis CI environment. Instead
of taking that long, we should end the abort test quickly,
after a test timeout. This will allow us to continue to
see the failure, only that the rest of the tests will be
executed, and no penalties to Travis due to inefficient
builds.

Of course, we still need to find the actual bug and fix it.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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

Fixes a sloppy copy and paste I made in the spec file.
Signed-off-by: NLucas Menghel Rodrigues <lmr@redhat.com>

GDB: use gdbserver --server-sdtderr option if available

GDB remote protocol support [v2]

A new command line option is being added to upstream GDB. This new
option allows gdbserver's own stderr (but not its inferior process
stderr) to be redirected to another file.

If that feature is available on the about to be used gdbserver, then
let's make use of it. This redirects its stderr to /dev/null, because
avocado itself has no real use for gdbserver's own stderr output.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

GDB talks to targets via a so-called remote protocol. These targets
can be things like gdbserver, ROM monitors on specific hardware boards,
or applications that implement the same protocol.

One noteworthy example of application is QEMU, which implements some
basic GDB Remote commands and also a few extenions of its own.

This initial implementation allows connecting to the remote target,
sending commands and receive results. The API can certainly grow later
based on demand.

Changes from v1:
 * Fix a typo in the REMOTE_MAX_PACKET_SIZE comment
Signed-off-by: NCleber Rosa <crosa@redhat.com>