When the Robot Framework finds an issue worthwhile to be shown on
the UI, it will do so, but that confuses Avocado users by mixing
the content from both layers.

Let's disable the Robot framework console logger, and only shown
the messages we intend to.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

1. read directly from /proc/meminfo.
2. improve the regex to get more accurate result.
Signed-off-by: Nlolyu <lolyu@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

This changes addresses the CVE-2017-18342[1] that defines: "In PyYAML
before 4.1, the yaml.load() API could execute arbitrary code. In other
words, yaml.safe_load is not used."

The change affects only installation using Python 3 because when
building EL7 RPMs, we want to use version 3.10, which is packaged on
EPEL.

[1] - https://nvd.nist.gov/vuln/detail/CVE-2017-18342Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

According to the author of the publication, the authoritative source,
we were using an incorrect URL to the publication that backs the CIT
implementation.  Let's fix that.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

This change adds a new utility function that receives a process id and
returns all processors (id) being used by the process (and its threads)
informed.
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

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

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

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

During the "make existing file tests" process of File Loader discover
method a broader exception is used because a lot of problems can be
found in this point. Regarding Python files, any exception can be
raised. When one of those exceptions was raised, the method
`_make_simple_or_broken_test` was being called without the third
parameter. This bug was added by the commit "cd818a8a".

Reference: https://trello.com/c/ggH77dKBSigned-off-by: NCaio Carrara <ccarrara@redhat.com>

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

The "discovery" with/without class_name given are really different
use-cases. Let's split them. Currently that means lots of redundant
code, but it'll allow some cleanups later.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  plugins.xunit: Format 'time' with 3 decimal places

Let's print the default value of --xunit-job-result option
on CLI help text.
Signed-off-by: NWainer dos Santos Moschetta <wainersm@redhat.com>

Any xUnit XML file when used to import test results in Jenkins CI
must comply to Ant and Maven's xUnit format specification. From
Jenkins' xUnit version 2.0 and up, the floating-point representation
of 'time' attribute should match Maven's surefire format
that restricts the use of at most 3 decimal places. But the Avocado's
xUnit plugin renders the 'time' attribute with several decimal places,
resulting in error to the load results.xml in Jenkins.

This change solves that problem by ensuring that the 'time' attribute
in Avocado's results.xml file is formatted with 3 decimal places.
Signed-off-by: NWainer dos Santos Moschetta <wainersm@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>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

Common location for contributing guidelines is "./CONTRIBUTING*" and
even github encourages us to use it. Let's symlink our documentation to
simplify first-time contributions (and also to make github happier).
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

ensure returns of service manager to be of type 'str'.
Signed-off-by: Nlolyu <lolyu@redhat.com>

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

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

Avocado requires the logging streams to be set before some calls. Most
critical ones are 'avocado.Test' related ones as without initialization
the:

    No handlers could be found for logger...

messages can cause infinite recursion. Anyway there are other places
where avocado loggers are called so let's set it on (hopefully) all
places (we have to treat some utils as well as for backward
compatibility reasons these utils use avocado loggers directly).

Note in functional tests this is not required as Avocado always setup
logging streams prior using those utils (otherwise the failure would be
a real bug).
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

Without this, the data files associated with the avocado_result_html
module won't be installed.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

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

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

On some situations, the same information may be given on tags that can
be reused during test runtime.  Let's create a property to allow a
test to read them.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Up to this point, the matching and thus filtering of tags was flat.
Now, the individual value of the required keys are checked.

For instance, if you have a test such as:

    class My(Test):
        def test(self):
            """
            🥑 tags=classification:tier1
            """
            ...

Both of these filter conditions will match:

 $ avocado run -t classification test.py
 $ avocado run -t classification:tier1 test.py

But this won't match:

 $ avocado run -t classification:tier2 test.py

Also, similarly to the how there's support for including tests that
have no tags at all, there's support for including tests that are
not tagged with a specific keys.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCaio Carrara <ccarrara@redhat.com>

Let's make the parsing of those tags a utility function so that its
behavior can be tested in detail.

Also, instead of parsing it for every test in a test suite, let's
parse those only once, and using during the filter process.
Signed-off-by: NCleber Rosa <crosa@redhat.com>