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>

The `python-avocado` package does not exists anymore, now we have py2
and py3 version. Let's check both and include the `src.rpm` as well.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Remote runner: provide fabric version for Python 3 on non-Fedora

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

* https://github.com/avocado-framework/avocado:
  selftests/functional/test_output_check.py: fix Python 3.4 syntax

tests or framework might need the name of the extracted archive to
perform necessary steps, it is better and harmless to return the name
in extract().
Signed-off-by: NBalamuruhan S <bala24@linux.vnet.ibm.com>

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

* https://github.com/avocado-framework/avocado:
  Travis CI: pin pylint version

Formatting bytes was only introduced on Python 3.5, so let's just
add the bytes. At the same time, there's no need for some of that
content to live in the module namespace, as only STDOUT and STDERR
are used later in the tests.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Avocado uses inspekt, which in turn uses pylint.  On Travis-CI under
Python 2.7, pylint 1.9.2 is being used, while on Python 3.4 it's
installing 2.0.0.

The pylint 2.0.0 API is different, and produces the following error:

   Running 'inspekt lint --exclude=.git --enable W0101,W0102,W0404,W0611,W0612,W0622'
   Pylint disabled: W,R,C,E1002,E1101,E1103,E1120,F0401,I0011
   Pylint enabled : W0101,W0102,W0404,W0611,W0612,W0622
   __init__() got an unexpected keyword argument 'exit'
   lint FAILED

Let's pin the pylint version for predictable results, as we do with
pycodestyle.

Reference: https://trello.com/c/LDbYJFeR/1374-lint-failed-on-python-3Signed-off-by: NCleber Rosa <crosa@redhat.com>

Fedora 29 (currently rawhide) has a python2-fabric3 package, so it can
use that (Fabric3) as a requirement on both Python 2.7 and 3.4+.  But
we have not switched to Fabric3 on other environments, so let's keep
the fabric (1.x) series there.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Asset Fetcher: avoid clashes by using namespace dirs
  Asset Fetcher: add a fetch/build example test
  avocado/utils/build.py: add a configure utility function
  Asset Fetcher: remove hashfile attribute
  Asset Fetcher: remove attribute asset_file
  Asset fetcher: remove public attributes nameobj and basename

The current implementation fails to cache multiple files if their
name is the same.  The filename *only* will be considered when
looking at the cached directories, and if hashes are not given,
users will end up with the wrong files, even when they give
unique URLs to different files.

To give a real example, suppose we have one test that needs a specific
asset file (such as an specific kernel version):

   def test_x86_64(self):
      self.fetch_asset('https://avocado-project.org/data/linux/x86_64/vmlinuz',
                       asset_hash='0123456789abcdef...')

While a second test wants the daily version of a given asset:

  def test_aarch64(self):
      self.fetch_asset('https://avocado-project.org/data/linux/aarch64/vmlinuz',
                       expire='1d')

If test_x86_64() runs first, it will write to $CACHE_DIR/vmlinuz.  The
second test, test_aarch64(), may end up having the completely wrong
file.  Using `asset_cache` is not a possibility, given that it wants
the daily kernel.

These changes put asset files on a "cache relative directory".  If a
hash is given, it's safe to put files in a directory indexed "by
name".  If not, they're put in a directory named after the URL (minus
the filename).
Signed-off-by: NCleber Rosa <crosa@redhat.com>