Signed-off-by: NAmador Pahim <apahim@redhat.com>

Signed-off-by: NAmador Pahim <apahim@redhat.com>

A few extra configurations needed for the Python 3 builds running on Travis-CI.
Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>

Merge branch 'travis_configuration_python3' of https://github.com/clebergnu/avocado into clebergnu-travis_configuration_python3

Instead of comparing a string against the exception, and relying
on its conversion to a string.  This approach is undesirable and
is caught by pylint on Python 3.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

That's the only sane way to handle data, as bytes.  Let's not assume
any enconding on them.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This lock doesn't prevent, say, multiple drainers from writing to
a single location.  It's not a cross-instance lock so I fail to
see how it has any purpose at all.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

It doesn't have a 'result_obj' attribute, but it does have a `result`
attribute which should be an instance of
`avocado.utils.process.CmdResult`.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

avocado.utils.process.system_output() is a utility function that has the
goal of returning the process output only.  Let's use it instead when
that's the only goal of the calling code.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This moves the tests that belong to plugins (remote and vm) to their own directories.
Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>

Because that version contains Python 3 syntax fixes.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

Move tests to the plugin's own directory.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Move tests to the plugin's own directory.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Merge branch 'move_yaml_to_mux_tests_v2' of https://github.com/clebergnu/avocado into clebergnu-move_yaml_to_mux_tests_v2

Merge branch 'epel_7_rpm_build_release_57_0_release_1_upstream' of https://github.com/clebergnu/avocado into clebergnu-epel_7_rpm_build_release_57_0_release_1_upstream

Merge branch 'tree_docs_tests' of https://github.com/clebergnu/avocado into clebergnu-tree_docs_tests

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

These classes and methods have knowledge about the YAML files, and the
YAML to Mux plugin is the only user of those.  this plugin.  So it
makes sense to move it to the plugin module.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

And drop the notion of a "multiplex capable" Avocado.  If the plugin is
installed, then we assume the dependencies have been fulfilled.  The plugin
presence is used then for the creation of the test suite, including the
plugin's own tests.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This drops the notion of a "multiplex capable" Avocado.  If the plugin
is installed, then we assume the dependencies have been fulfilled.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

This change enables plugins tests to also be run in parallel, if
they exist.

Because the "selftests/{unit,functional,doc}" directories are valid
Python modules, that is, they contain `__init__.py` files and can
be imported by the unittest runner, no special handling is necessary.

But, since the complete path for directories which (can) hold plugins
tests are not valid Python modules (and shouldn't be), some special
handling of directories is necessary.

Because of that, it's not currently possible to run *all* of the
tests (from "core" selftests and from plugins) at the same time.
A future enhacement would be to better schedule processes that
can be loaded from the same path at the same time, but all of
them at once with global "test slices".
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

So there are no clases in history of RPM releases.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Some versions of the unittest mock library cannot easily deal with
(builtin) open().  Let's skip these tests on those platforms, instead
of coming up with cumbersome code to support them on all (ancient)
versions.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

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

Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

* https://github.com/avocado-framework/avocado:
  Docs: update location for RPM repo location

We've got a new server, and the RPM repo is already there.  Let's use
that new server in the documentation.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

Some packages are specific to Python 2.7, such as mock which already
exists in the Python 3 standard library.

Also, commit fb98d386 removed the cyclical_deps check from Python 3
environments, because the requirements to run it are not available on
Python 3.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The goal of this change is to inspect how Python 3 compatibility plays
in the Travis-CI environment, while not blocking the supported Python
2 builds.

IIUC, when using "system_site_packages", we're stuck with the Python
version on Ubuntu Trusty (2.7.6 and 3.4.3).  That's the reason behind
the specific "3.4" version added there.

[1] https://docs.travis-ci.com/user/languages/python/#Travis-CI-Uses-Isolated-virtualenvsSigned-off-by: NCleber Rosa <crosa@redhat.com>

The 52lts branch is missing in the configuration file.  Let's add it.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

According to https://docs.travis-ci.com/user/languages/python, the
standard way of setting up that configuration is by using the
"system_site_packages" under "virtualenv".

It looks like the current syntax was a valid fix for a Travis-CI
issue that is now fixed, and it was being used in Avocado to support
the now dropped Python 2.6 version checks.
Signed-off-by: NCleber Rosa <crosa@redhat.com>