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

* https://github.com/avocado-framework/avocado:
  Makefile: Make sure to use pip of the same version as python

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

Some systems don't ship with "pip" binary and only provide the "pip3".
Instead of attempting to get the right one, let's just use "python -m
pip" that should work the same way plus we always use the right version
(py2/py3).
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  CIT Varianter

Avoid IndexError in case of empty archive.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Recently the archive library started returning first file name, let's
adjust our selftests to make sure it works.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Remove requirements file for readthedocs.org
  Makefile: move generic enough targets to Makefile.include
  Makefile: add RPM_BASE_NAME variable
  Makefile: add PYTHON_MODULE_NAME variable
  Makefile: add ARCHIVE_BASE_NAME variable
  Makefile: add all configuration variables to "variables" target
  Makefile: change the rule to make sure pip is available

Implementation of the CIT varianter optional plugin.
Signed-off-by: NAmador Pahim <amador@apahim.org>
Signed-off-by: NCleber Rosa <crosa@redhat.com>

During the last release (63.0), readthedocs.org builds were failing,
complaining about the non existence of "requirements-docs.txt".

After escalating the problem, I decided to remove that option from the
configuration system.  The result was a successful build.  I can only
assume that readthedocs.org have everything we need.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This will allow us to reuse the `Makefile.include` on other projects,
such as Avocado-VT.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

To make the targets related to building RPMs configurable and
reusable.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

To make the rules that deal with Python modules configurable and
redistributable.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Which is intended to told the base name of the archives generated by
rules such as "source".

The idea behind making them configurable is that the rules can then be
put in files to be included here, and kept in better sync across
Avocado projects.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

And make sure they are in order to ease the comparison of possible
with new variables.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Since Python 2.7.9, it's possible to use the "ensurepip" module to
check and bootstrap pip at the same time.  Then, only if that is
not available, we'd try the old bootstrap recipe.

Reference: https://docs.python.org/2/library/ensurepip.htmlSigned-off-by: NCleber Rosa <crosa@redhat.com>

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

package dependencies are available.
Signed-off-by: NMerlin Mathesius <mmathesi@redhat.com>

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

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

`examples/tests/simplewarning.sh` calls a generic avocado command,
which gets added to the path by the test code. That generic avocado
command is `scripts/avocado`, from the source repository, which
contains the unversioned `/usr/bin/env python`.

Under some environments, such as Fedora >= 29, there may be no
unversioned Python binary.  Let's respect the UNITTEST_AVOCADO_CMD
environment variable, and add the the directory containting that
binary to the PATH.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

Raising StopIteration gets translated to a RuntimeError in Python 3.7.
The same behavior can be achieved by 'return' from generators.

Reference: https://github.com/avocado-framework/avocado/issues/2721Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NAmador Pahim <amador@pahim.org>

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

* https://github.com/avocado-framework/avocado:
  Travis-CI: add jobs for nightly versions of CPython
  Travis-CI: add Python 3.5 and 3.6 jobs
  Travis-CI: remove "system_site_packages" option

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

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

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

Signed-off-by: NMerlin Mathesius <mmathesi@redhat.com>

Signed-off-by: NMerlin Mathesius <mmathesi@redhat.com>

Given that the implementation of the code to find Avocado Instrumented
Tests is already quite big, and that a good part of it already lives
in the safeloader module, let's complete the move.

This sets the tone of having the generic loader mechanism in the
"avocado.core.loader" module, while having implementations, at least
for the instrumented test at this point, in the "avocado.core.safeloader"
module.

With this change, the loader knows nothing about ast, and relies on
safeloader.find_avocado_tests() only.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Add method to set/get cpu frequency governor

Add method to set given cpu frequency governor systemwide
and choose a random available one if special governor value
`random` is given and method to get current cpu frequency governor.
Signed-off-by: NSatheesh Rajendran <sathnaga@linux.vnet.ibm.com>

Which should help us, for now, to keep an eye at what may become a
problem for Avocado.  Given that development versions of anything are
bound to break, let's allow failures for that specific job.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

3.7 is still not available as a "package" to be downloaded on the
Travis CI environment.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The "system_site_packages" option is needed when the Python
installation on the virtual environments need to access Python
packages outside of them, that is, on the system.  Given the
environment in which Travis-CI jobs run, this means packages installed
via apt, and not via pip.

While we do install packages via apt, we install libvirt-dev, and
install libvirt-python via pip.  In summary, we do not need that
option.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

The "avocado-server" is not being actively developed, still we spend 2
extra manual steps on trying whether it works. Let's stop and depend on
user-input.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

There are 5 extra steps every release on "avocado-virt" which is not
actively developed. Let's stop that and depend on user-inputs.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The "aexpect" package should be installed from distribution, there is no
need to build it nor install from additional repositories.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>