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

And not "asset_file", because that references the file with the
content itself, and not the file containing its hash.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Which helps us to better document, also in the avocado.Test class
itself the hash algorithm that will be used by default.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Instead of raising a generic exception about not being able to fetch
the file, let's tell the user upfront that the protocol is not
supported.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

By using a common interface, and choosing the function to use based on
the protocol (aka scheme) some duplicate code can be removed.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This improves readability, removing on indentation level and bringing
the exception raised when no writable cache dir exists, (much) closer
to the code that checks for them.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The asset fetchers cache directories are system wide, and not test
specific.  They're available at the test only for convenience.

They relate much more to the the other data directories, and deserve
to be visible by users alongside the other data directories.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The author probably meant "search" and not "find".
Signed-off-by: NCleber Rosa <crosa@redhat.com>

It adds no real value on top of hashlib.new(), only imposing virtual
limitations that do not map the real list of available hash
algorithms.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The parameter for the hash algorithm is "algorithm", and not "method".
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Update documentation to reflect relocated examples.
  Update avocado.conf to reflect relocated example tests.
  SPEC file: Relocate examples to doc directory to prevent inclusion of python version-specific byte-compiled files in package.

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

* https://github.com/avocado-framework/avocado:
  Add methods to get/set cpuidle states

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

* https://github.com/avocado-framework/avocado:
  selftest: Fix line-wrap

Add methods to get/set cpuidle states
in host and selftests for the method.
Signed-off-by: NSatheesh Rajendran <sathnaga@linux.vnet.ibm.com>

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

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

* https://github.com/avocado-framework/avocado:
  Added method to get NUMA nodes with memory

This patch adds method to get list of nodes with memory on given
machine.
Signed-off-by: NHarish <harish@linux.vnet.ibm.com>

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

* https://github.com/avocado-framework/avocado:
  Add comma_separated_ranges_to_list utility

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

Fedora 28 changed the URL of the Cloud Images, from "CloudImages" to
simply "Cloud".  Let's adapt the name depending on the version
requested.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Patch adds comma_separated_ranges_to_list utility to return a list
of integers from comma separated range values
Signed-off-by: NHarish <harish@linux.vnet.ibm.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>

On some architectures, Python will return a long on
data_structures.DataSize conversions.  That makes the identity
check assertion fail, because:

   >>> long(0) == int(0)
   True

But:
   >>> long(0) is int(0)
   False

Reference: https://kojipkgs.fedoraproject.org//work/tasks/1223/26881223/build.logSigned-off-by: NCleber Rosa <crosa@redhat.com>

python version-specific byte-compiled files in package.
Signed-off-by: NMerlin Mathesius <mmathesi@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>

* https://github.com/avocado-framework/avocado:
  Python 3: fix re.search() using string pattern on a bytes-like object

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

* https://github.com/avocado-framework/avocado:
  utils.partition: Use encoding instead of bytes
  test: Allow unicode in exception (and tests results in general)
  utils.astring: Allow converting any object "to_text"
  utils.astring: Use prefered encoding as default to `to_text` method
  utils.astring: Add preferred ENCODING

re.search(regexp, out) need regexp and out in the same type:string or bytes
currently regexp is string,but out is bytes,which throw TypeError
Fix this issue by transfering out into string forcedly
Signed-off-by: Nchunfuwen <chwen@redhat.com>

* move man pages into common package
* claim ownership of all config and content directories
* Python version-specific packaging of avocado-rest-client
Signed-off-by: NMerlin Mathesius <mmathesi@redhat.com>

The mountpoints are user-facing values and should be reported decoded.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Currently Avocado crashes on py2 when the exception contains unicode.
Let's use the new "astring.to_text" method to safely get the exception
details.

As this exception is part of the results, this commit also fixes the
result plugins to cope with unicodes in them.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Previously the "astring.to_text" correctly handled bytes or string
types. This commit allows using it to convert anything to text. The
use-case is to turn any object into string in a safe manner, which is
useful to replace "str(...)" calls on python2 which fails with unicode
while working well on py3 as well.

Note it's not necessary to convert all "str(...)" calls as objects that
use "__repr__" are usually safe and "astring.to_text" becomes equivalent
of "str(...)", but for objects (eg. Exception, ...) the
"astring.to_text" is required.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Most frequently people want to convert to the prefered encoding. Let's
avoid the need to specify the encoding in such cases and require
encoding only when different one should be used.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

There is no right encoding, but the `locale.getpreferredencoding` suits
most cases. Let's avoid the usually unnecessary `locale` import and
people struggling to remember the most appropriate method and store it
in `avocado.utils.astring`.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

* selftests/unit/test_xunit.py: also output schema validation errors
* selftests/unit/test_xunit.py: junit XSD file is only used in one test
* selftests/unit/test_xunit.py: specify JUnit variation used
Signed-off-by: NWainer dos Santos Moschetta <wainersm@redhat.com>

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

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

* https://github.com/avocado-framework/avocado:
  Python 3: fix re.findall() using string pattern on a bytes-like object