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>

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>

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

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

* https://github.com/avocado-framework/avocado:
  python 3 : Journalctl collection failed issue

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

json.loads(xx) on python 3 need string object
out_journalctl open in text mode but bytes passed in
Simply fix them by forcing to string and open in bytes mode
Signed-off-by: Nchunfuwen <chwen@redhat.com>

On Fedora 28, if a Python 2 script is invoked with "/usr/bin/python",
it will produce a warning like this:

   DEPRECATION WARNING: python2 invoked with /usr/bin/python.
       Use /usr/bin/python3 or /usr/bin/python2
       /usr/bin/python will be removed or switched to Python 3 in the future.
       If you cannot make the switch now, please follow instructions at https://fedoraproject.org/wiki/Changes/Avoid_usr_bin_python_in_RPM_Build#Quick_Opt-Out

Let's tell the unittests explicitly to use the versioned script,
created during the "pythonX.Y setup.py develop --user" step.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Used during the %check phase.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

When a plugin is not installed, its command line options are not
registered with the optparse based code.  That is caught earlier than
Avocado's own handling of incompatible options (in this case, the replay
and the remote runner), and results in the errors such as:

  avocado run: error: unrecognized arguments: --remote-hostname

When building RPM packages for Python 3, the remote runner plugin is
not available, and this test should be skipped.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The "--old-chroot" command line option was added right after the
chroot model was changed in Fedora and was causing build failures.

It now seems to perform OK, so let's use the "current" chroot method.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

On b97a4cfa, the (noisy) output produced by the inspekt lint (and
underline pylint) was silenced by having it redirected to a file.

This seems to no longer be necessary.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

The 'avocado list -V' prints the list of tests as a matrix with
Type, Test and Tag(s) columns. Some lines may get trailing
whitespace chars due the method used to align the columns' value.

Changed the call to avocado.utils.astring.iter_tabular_output()
so that trailing whitespace are removed from each row.

Adjusted the PluginsTest.test_list_no_file_loader() test due lack
of whitespace on outputs to be compared.

Reference: https://trello.com/c/JWeay87z/1045-strip-tabularoutput-linesSigned-off-by: NWainer dos Santos Moschetta <wainersm@redhat.com>

Signed-off-by: NWainer dos Santos Moschetta <wainersm@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  python3: fix 'str' does not support the buffer interface

Fix issue:Log file /var/log/messages collection failed: 'str' does not support the buffer interface
Signed-off-by: Nchunfuwen <chwen@redhat.com>

Added 'strip' parameter (default False) to avocado.utils.astring's
iter_tabular_output() and tabular_output() methods that strips
trailing whitespace of rows on the tabular output.

Also introduced unit tests for those methods.
Signed-off-by: NWainer dos Santos Moschetta <wainersm@redhat.com>

It's not easy to find one definitive specification for the the JUnit /
Xunit formats, and a number of different schemas have been published
by different entities.

The current schema version we ship was based on a repository that is
no longer available.  Even though the format is exactly the same,
let's switch to the schema hosted by the JUnit project, and to what
is considered the Jenkins schema (as part of the JUnit 5 project).

Reference: https://junit.org/junit5/
Reference: https://raw.githubusercontent.com/junit-team/junit5/master/platform-tests/src/test/resources/jenkins-junit.xsdSigned-off-by: NCleber Rosa <crosa@redhat.com>

So it makes no sense to use in the setup phase.  Let's move that
closer to its actual usage.
Signed-off-by: NCleber Rosa <crosa@redhat.com>