avocado: Fix renamed attribute from avocado.core.output

The reference was incorrect, causing some of the plugins
to crash.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Version 0.10.0

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

The tests dir layout has changed, update setup accordingly.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Test feedback 2

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

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

This calls os.abort() as the test action, testing avocado
ability of handle this case correctly.
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>

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

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

Previously, the throbber update method was being called
unconditionally, making throbber progress to appear even
when human output was not enabled. Fix this by making
a proxy method that calls it only if there is a human
plugin enabled, in TestResultProxy.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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

Put state of the initialized test in the multiprocess Queue,
so we have a lot of accurate information that does not need
to be mocked, we only have to mock the failure reason and
time elapsed. With this, aborted tests can be handled more
gracefully.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Introduce a TestAbortError, used for when an avocado test
aborts.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

If the test process is running, the trobber will give feedback about that
to the user.

This requires the process triggering and timeout handling to be completely
different than the previous implementation.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

It's now a known fact that long test runs are can lead to doubts with
regards to the actual test run status (is it frozen or really busy?).

To give users a better experience, the OutputManager now implements
a throbber for progress feedback.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

In some circurnstances, the journal may be accessed simultaneously by
multiple code paths. The database consistency should be enforced in any
case, and only initialized and populated when appropriate.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Since other more standard plugins have moved to test state in a previous commit
the journal plugin should also follow that.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

This commit implements two very different things, but still very
much connected:

1) Separate test loading to the process that will be actually
running the test. This leads to a better separation of duties of
the process interacting with the user and the process that is
actually doing the (usually) heavy work.

2) Remove the pickling of the test instance and sending it back
and forth.

As an added bonus, it was noted during development, that both
processes load all necessary Python modules (including the test
module) when unmarshalling the pickled instance, resulting in
unecessary work. Actual data on performance improvements were not
collected though.

It has one change in behaviour (regression) though. Test timeout
now comes only from the test parameters. The reasoning is that
since there's now a better separation of roles and the fact that
the first process is not loading the test instance, it can not
look at the timeout defined there.

IMHO this is a sign of good design, since other types of test
(think of shell scripts) can not communicate their intended timeout.
Maybe a 'test.cfg' or something like that should be the solution to
that.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

docs.source.WritingTests: Introduce environment variables.

Add new subsection about environment variables that
Avocado exports to the tests.

Plus fix some typos.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

avocado.test: export environment variables to tests.

Export environment variables to the running test.
Really effective when using drop-in tests, that can make use of shell
variables "AVOCADO_*".

Example:

Export variable AVOCADO_VERSION with the current version of Avocado,
then the drop-in test can use $AVOCADO_VERSION within, and so on.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

Fix vm plugin

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

So the vm plugin can correctly determine the logs dir.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

We missed that on the whiteboard work.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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

multiplexer plugin: simple usability fix

Flat tests

Packaging fixes

Make avocado tests to refer to their test ids (paths),
relative to the directory you are in. For example,
running:

avocado run tests/sleeptest.py

will give you

DEBUG LOG: /home/lmr/avocado/logs/run-2014-07-31-12.54.01/debug.log
TOTAL TESTS: 1
(1/1) tests/synctest.py.1: PASS (1.93 s)

Test log and data directories were changed accordingly. Now,
if your test is synctest.py, your data dir will be called
synctest.py.data.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Since the multiplex file is a positional argument, we can not say
it's a required parameter, but we can and should check that at
least one was provided.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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