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

This basically means that any pushes to the 69lts branch will also
generate a new Travis CI job.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

And by removing the data, we won't have any test to be run, so
we're also removing the test itself.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

We only run tests on Python >= 3.4, so let's not attempt to support
anything else.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The E1136 (unsubscriptable-object) error on pylint is described as
being "emitted when a subscripted value doesn't support subscription
(i.e. doesn't define __getitem__ method or __class_getitem__ for a
class)".

But that is not the case here, so assuming it's a false positive,
let's ignore this check.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

It was introduced in 8f8d668b, but stoped being used in 6681f2d6.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

There's no need for the first assignments to the `TERM_SUPPORT`
and `STD_OUTPUT` variables.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Commit 9401c928 removed Python 2.6 support, but this bit remained.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

The pylint version in use requires a specific version (or a not
so greater version) of astroid.  When the astroid version is not
pinned, astroid version 2.2.4 currently gets installed.

Then, pylint (and thus inspektor) fails with:

  'Import' object has no attribute 'infer_name_module'

Let's bump the pylint version (already pinned) and pin a compatible
astroid version too.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

Commit 72f9bb10 removed default_params, but it was not reflected on
examples/tests/abort.py example tests.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The log files produced for the root logger are confused with hidden
files (.INFO, .DEBUG, .WARN, .ERROR) because the root logger's name
is an empty string.
Signed-off-by: NPlamen Dimitrov <pdimitrov@pevogam.com>

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

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

Those are the packages for the latest releases, so there are
more packages than previously listed.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Those are the packages for the previous LTS (52.0) version, so the
number of plugins are somewhat limited.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

There are more plugins on pip than the ones we're listing.  Let's
update the list of the currently available plugins.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

netifaces is an external library, that is not trivially installable by
pip (requires a C compiler).  Let's make the test conditional to the
presence of the netifaces library.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

In the parallel execution, not honoring the Python version used
elsewhere may cause unexpected issues.  One is an error situation in
which Python 3's unittest.loader can not load an exception definition
that exists only Python 2.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This new playbook installs Avocado and Avocado-VT from RPM packages
from a Copr repository that follows the project's master branch.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Avocado-VT is a separate project, but it's a very important one,
and it should always be kept working with Avocado.

This adds the Python dependencies that are hard or impossible to
install via PIP, and so that they're available on the virtual
environment, a "site packages" options is set.

We then bootstrap Avocado-VT and finally sure that one of the common
tests is present.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This includes Python packages and a a virtualenv script for systems
that lack them.
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>

Instead of a stringified version of Python's version of null,
that is, "None".

The generated JSON file is consumed by the remote test runner,
and given that the failure reason is a valid string, it's shown
in the Human UI.

Reference: https://trello.com/c/ihTDNdov/1472-bug-remote-vm-runner-prints-none-on-pass-resultsSigned-off-by: NCleber Rosa <crosa@redhat.com>

Each test has its own log file within a given job result dir,
located at "test-results/$(test-id)/debug.log".

If the test is an INSTRUMENTED test, using the standard Python logging
module/API, all produced content should be recorded into the test log
file.  This adds a handler that does exactly that to the logging
module root logger.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

The fake-vmstat process should run for infinity. Using wait with 1s
timeout will eventually destroy the test after the timeout, but cleaner
solution is to explicitly terminate it and then use the wait to make
sure it finished (or eventually nuke it)
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Let's publicize the COPR repo, both how to use it and the build
status, on our docs.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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