In case no suitable jobdir location can be created (user basically can't
write anywhere) Avocado crashes without a meaningful message, let's
provide one.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The user-config location ("~/.config/avocado.conf") might not be
writable by users (usually when executing in docker without user
home-dir). Let's use the file if available, but don't fail in case we
fail to produce it.
Signed-off-by: NLukáš Doktor <ldoktor@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>

With the recent changes the "libexec" dir is only available when
installed via RPM. In order to have "libexec" files available
as standard package we have to include it in  the package_files
dir (avocado/). The benefit is that we can actually use package
resources to get the location in "avocado exec-path" command.

For packaging purposes let's simply symlink $libexec/avocado to the
packaged $avocado/libexec location so there is the usual location, but
keep using the python-location by default.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

With the python3 patches we have another core dependency on six. Let's
include it in setup.py as without it Avocado is unusable.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

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

We increased the failed_once threshold, let's see whether Travis will
behave better now.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The "realpath" is being deprecated in favor of "readlink -f", which
should mainly work the same way. This is required by Travis as it's
version of Ubuntu does not contain "realpath".
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

In Travis more tests are failing when running in parallel, but still 20
failed tests in parallel re-ran in series are faster than all tests in
series.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  utils.cpu: Update cpu info pattern for aarch64

arm64 or aarch64 pattern is not easy to identify in the
cpuinfo. For v7 there is model name in the cpuinfo and it
could be regonize as arm for 32 bit. But in v8 only could
found 'CPU architecture' in the cpuinfo and current code
will fail to match and return i386 which is wrong.

For fix this, if 'CPU architecture' found in cpuinfo, use
platform.machine to return the arch name.
Signed-off-by: NWayne Sun <gsun@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Packaging: add bash RPM sub package
  Packaging: remove man page sources from binary RPM packages
  Packaging: remove examples from Python side of installation
  Packaging: remove unused function _get_resource_files()
  Settings: remove variables from the main module namespace
  Packaging: exclude optional_plugins tests in addition to selftests
  Packaging: add missing configuration files for RPM packages
  Packaging: make config files data files of the avocado module

To remove some of the bloat (even if little) of the base
python-avocado package, let's move content that is not useful to
Python developers out of the way.

This should also make the experience of content more similar across
users of the Python module (say, from a `pip install`) and users of
the python-avocado package.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

There's little to no point in providing these files, since the
generated man pages are already packaged.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Leaving them only in the source distribution generation (if one runs
python setup.py sdist) and in the "example" RPM package.

Because the copying of those files won't be performed by the Python
module installation code, it must be done in the SPEC file.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

The main module namespace has a lot of variables which are only
used in the main class initialization method.  Let's avoid poluting
the module namespace and move those to where they're used.  If
we want to put variables at the global module namespace, we
should consider if they're useful to other modules, make them
all caps, and document them.

A nicer refactor could be done here, but IMO, this is still an
improvement.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The selftests from the main source directory (and package) are already
excluded from being considered modules to be distributed.  Let's also
exclude the tests that have recently been moved to their own modules.

Without this change, the "tests" module will be installed in Python's
library location, and will contain the files from all of those
directories.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

These files weren't being installed by the setup.py code, and thus
ended up missing from RPM packages.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

In a pure Python world[1] the "avocado" module requires the existence
of these configuration files.  Let's make those configuration files
"data files" of that module.

Since the configuration location can now be a different, the settings
module needs adjustments to also attempt to load them from package
resources (which is tied to the data files).

Finally, when using RPM packages, we need to put the configuration
back into the system location (/etc).

[1] - that is, ignoring operating system or distribution specific
      conventions and packaging technologies
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  avocado/core/job.py: don't attempt to run git if .git doesn't exist
  Revert "avocado/core/job.py: don't attempt to run git if .git doesn't exist"

When looking for the GIT commit info to log in the Avocado job log,
we can optmize things a little by not running git if the ".git" directory
doesn't exist at the top level.

py2to3 is not being used anymore, so we don't need to check if we're
running from modules from the build directory.

Also, as another optmization, let's not look for the git binary until
we're sure we'll be running it.

Update: Use abspath to get "base_dir" location to avoid using "" when
avocado is executed from main git directory.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The 6323773d commit breaks avocado
execution from head of the git source as the base_dir is "" and then
"os.chdir" fails.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

If the avocado repo file is not in the system, we can
simply create the repo file. This patch fixes a bug
when trying to access the file for reading will throw
a file not found error.
Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>

'apt update' does require sudo to run.
Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>

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

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

yumdownloader might ask some questions, let's use "--assumeyes" to avoid
hangs.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Currently it uses "--urls" to list urls to download from and then it
initiates another execution to get the actual file. This is potentially
dangerous as the name can change between those two executions.

Due to yumdownloader bug it's not possible to get the downloaded file
name from python execution (as in non-TTY mode it's not printing it on
<F26) let's use tmpdir and assume the only existing "src.rpm" there is
the freshly downloaded one.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

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

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

When looking for the GIT commit info to log in the Avocado job log,
we can optmize things a little by not running git if the ".git" directory
doesn't exist at the top level.

py2to3 is not being used anymore, so we don't need to check if we're
running from modules from the build directory.

Also, as another optmization, let's not look for the git binary until
we're sure we'll be running it.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Let's break down the types and description of the CmdResult init
method.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

We're (hopefully) about to change the specifics about the Python
versions we support.  But, until then, let's be clear about the
Python version (2.7) that we support.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

pyliblzma is not required in python >= 3.3, and backports.lzma
works for all versions prior to that one. Let's update
the requirements.txt file to only install that backport
when necessary.
Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>