The option --relative links instructed the htmlresult plugin
whether to use absolute log paths in anchor tags, or to use
relative paths, something that dates back to the old autotest
html job report. After thinking about it I realized that this
option doesn't need to be here, as using relative links is
basically better for all intents and purposes (the job results
can be safely redistributed and the report would still work).

So get rid of that option and always use relative links for
the job results dir links and logs. Tested with local execution
as well as remote/vm execution.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Remove another seldomly used option, --job-log-level, and
move the opportunity to set the value to the config file.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

It is not a widely used option, so it's better to keep it
in runner.behavior.keep_tmp_files config.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In the local runner, we use the multiplexer, but not so
in remote runner mode. Let's add the compatibility option
here to resolve the bug that broke the remote plugin.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Review command line options. [V5]

avocado.job: Refactor how multiplexation happens [v3]

This pull request changes the way multiplexation is used.

1. tests are discovered by test_loader.discover()
2. multiplexer is initialized
3. suite is executed with initialized multiplexer class
4. each test works as template and iterates over multiplexer variants

Additionaly support for multiplex_files overriding was removed as I
haven't found any users of this API.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch is initial support for people using custom bash scripts
with avocado. Tests should use:

    PATH=$(avocado "exec-path"):$PATH

and then they can utilize the helpers.

This version contain functions to write to Test.log the same way it's
possible from python including failing the test with TestWarn in case
avocado_warn was used.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

No actual change, only refactor code to use single function to get all
paths.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

avocado.job: Print test results dir even on --show-job-log

We were printing the results dir only when standalone test
mode was used. Let's extend that to --show-job-log as well
by moving the message to the end of the job execution
method.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

When no tag is supplied get_tagged_name() generates unique name. On the
other hand when tag is supplied, it silently reuses existing path. This
patch adds check for these cases and use $name.$tag.$number in case
$name.$tag exists.

This should avoid clashes when executing multiple tests with the same
name with multiplexation.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

No actual change, only merge 2 same branches together.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Validate options from `--job-log-level`.
Plus cosmetic change in `--output-check-record`.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Use `--paginator {on,off}` instead of `--disable-paginator`.
It is on by default, set `--paginator=off` to disable it.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Group together jsonresult, xunitresult, htmlresult and journal
inside "output related arguments".

Side effect: export `self.parser.runner.output` to the plugins.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Add command line `--job-results-dir` to the Avocado runner, so we can
store the job results in a different directory than the one
configured.

Remove `--logdir` from the main avocado application,
this option is obsolete and actually it was not working.

Update the manual page regarding this change.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

From the current command line `--disable-output-check` replace it
with the new command line `--output-check {on,off}`, defaults to `on`.

Use `--output-check=off` to behave like ``--disable-output-check`.

Also, validate the value from command line `--output-check-record`.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

From the current command line `--gdb-enable-core` replace it with
the new command line `--gdb-coredump {on,off}`, set default to `off`.

Use `--gdb-coredump=on` to behave like `--gdb-enable-core`.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Write a proper help message to option `--wrap`.
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>

Makefile: have a better target/recipe with deps for man pages

The `man` target is not currently using make's dependency system, let's
fix that.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Print Job ID in job log

The job ID is an important information that should've
been printed to our job log. This patch fixes it and
also adds a functional verification test.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

It is more natural [1] that output of --show-job-log goes to
stdout than stderr. Let's change that behavior and update
unittests accordingly.

[1] Natural in this sense is defined by the user's expectation -
    when setting avocado to --show-job-log, you expect that the
    job log *is* in the application's stdout.

Changes from v1:
 * Python 2.6 constructor param for StreamHandler is strm,
   that was changed in 2.7 to be stream. Let's keep compatibility
   by using positional arguments.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Turns out that depending on guest config options, sometimes
the paginator kicks in and won't release the stdout until
a human comes in and presses 'q'. This is very, very bad for
automated procedures such as the one used by the remote plugin.

So add --disable-paginator in both plugins that use that
functionality, so they can be used in automated scripts.
Afterwards, we'll use that option in the remote plugin.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Under .el6, we depend on a series of EPEL available backports,
so we have to define the dependencies conditionally. The
changes here make avocado to finally build on RHEL6/CentOS6.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Add a new python 2.6 target so that we can make sure
avocado works on older distros (our specific focus here
is RHEL 6, but of course, we expect the work on RHEL 6
to be useful to other distros sticking with older versions
of the python runtime).

In order to do that, we added a new 2.6 related requirements
file, and changed the requirements a bit so that it all
works under the particular Travis CI environment.

Changes from v1:
 * Per ldoktor's suggestion, use conditional install of backports
   using $TRAVIS_PYTHON_VERSION
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Python 2.6's os.path.relpath function returns some funny
results, such as:

In [3]: os.path.relpath('/tmp', '/')
Out[3]: '../tmp'

So let's skip relpath entirely.

Changes from v1:
 * Per ldoktor's suggestion use lstrip('/') instead of
   relpath workarounds.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

We can't install libvirt-python using pip since the
VM used by Travis runs Ubuntu 12.04 LTS (libvirt headers
are too old), so we have to settle for not requiring
all plugins (VM) to be available. It will still be tested
on 2.7, though.

Changes from v1:
 * Per ldoktor's suggestion, change check of exact python
   version being 2.7.x to python version >= 2.7.0.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

This one uses --vm, which is redundant and also uses
the vm functionality, one thing we still can't do in
Travis.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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