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

Previously we were directly using the yaml.Loader, which is shared
across all `yaml` instances. This patch creates a `_BaseLoader` with the
basic set of constructors. That one is copied and updated of the
run-time data (debug/non-debug) during the `_create_from_yaml` to allow
loading debug and non-debug files in a single execution without
overriding the same loader.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The requirement is meant only for the runner remote plugin, and not
for the base avocado package.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Remove the TESTS line from the UI

This information is not accurate since it does not consider the number
of variants. Also, if it was accurate, it would be redundant.

Let's just remove it.  

Reference: https://trello.com/c/62I3ABZ0Signed-off-by: NAmador Pahim <apahim@redhat.com>

fabric code as packged by Fedora 24 requires python-crypto, but
does not set this as a package requirement.  This prevents package
builds on this distro version.
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: NCleber Rosa <crosa@redhat.com>

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

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

The virt/vt plugin names contain '-'s and not '_'s.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

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

The job has the number of tests, but not the total of test executions.
This information comes from the result attribute 'tests_total', updated
by the runner.

This patch changes the tap plugin so it can use the correct information.

Reference: https://trello.com/c/tiusKNNjSigned-off-by: NAmador Pahim <apahim@redhat.com>

The start_tests() method from results plugins is not used anymore. It
was replaced by the pre_tests entry point in plugins_interfaces.

This patch is just a cleanup.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Remote/VM/Docker: make them optional plugins
  Docker CLI plugin: remove LOG instance that is possibly unused
  VM Runner:  remove unused logger instance
  VM Runner: assume dependencies are fulfilled
  Remote Runner: do not mask avocado.core.output module
  Remote Runner: removal of RemoteTest
  Remote Runner: assume dependencies are fulfilled
  Remote: remove unused logger instance
  Travis: pin setuptools version

Our users have pointed out that the basic Avocado test runner, and its
related packaged form, has too many dependencies.  They're absolutely
right, and the whole goal of having plugins in Avocado is that
dependencies can be made optional according to the features required
by a given user.

This specific change creates three new optional plugins, containing
the extended test runners: remote, vm and docker.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  adding a line to pci.py to skip System peripheral device in output

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

* https://github.com/avocado-framework/avocado:
  Return slot direct from file output without any filter

We already tweaked the "make link" to not fail when "make link" fails
but I forgot about unlink, which is now failing. Let's allow the "make
link" failure as there might be non-related modules not implementing the
"make unlink" functionality.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

This topic seems to fit this section and could be useful to people
previously using this feature.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The whiteboard is a neat feature to avoid boiler-plate code and to
improve the results structure. But in one of the recent presentations
about Avocado I saw a usage which was not really inlined with how this
feature work so let's explicitly mention it's convenient, but not
intended for cases where the system might crash (or so).
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This information is quite low level and is also mentioned on the same
page in `Execution Model` section.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Different servers returns the slot numbers in different formate.
So filtering it with regExp may not return correct value.
hence return a slot value directly from file output, and leave
upto the user for rheir usage accordingly.
following are few example of different slot values on different
systems
examples:
root@ltciofvtr-firestone1:~# lsvpd -l 0000:01:00.1 | grep -i "*YL"
*YL Slot5
root@ltciofvtr-firestone1:~#
root@ltc-briggs3:~# lsvpd -l 0004:01:00.1 | grep -i "*YL"
*YL WIO Slot3
root@ltc-briggs3:~#
root@ltcalpine-lp2:~# lsvpd -l 0028:01:00.0 | grep -i "*YL"
*YL U78C7.001.RCH0040-P1-C9-T1
root@ltcalpine-lp2:~#
Signed-off-by: NNaresh Bannoth <nbannoth@in.ibm.com>

lspci output lists System perpheral deivece's pci address too,
like PCI Bridge, which are not much operable by end user. Hence
skipping them while parsing the pci adress to the user.
these deivce looks like as follows
*XXX:XX:XX.X System peripheral: PLX Technology, Inc. Device 87d0
example:
root@ltc-briggs3:~# lspci -D | grep -i peripheral
0001:01:00.1 System peripheral: PLX Technology, Inc. Device 87d0
0001:01:00.2 System peripheral: PLX Technology, Inc. Device 87d0
0001:01:00.3 System peripheral: PLX Technology, Inc. Device 87d0
0001:01:00.4 System peripheral: PLX Technology, Inc. Device 87d0
root@ltc-briggs3:~#
Signed-off-by: NNaresh Bannoth <nbannoth@in.ibm.com>

Minor style and optimization change, where the module level LOG
instance may not be used depending on code path.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

In the same spirit of the changes to the Remote Runner, let's assume
that dependecies are fullfiled because the VM Runner will soon become
an optional plugin.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The avocado.core.output module is imported with name `output`
which is then masked by the variable name in the scope of this method.

Small issue that is currently harmless, but it's still better to
avoid those name clashes.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

While going through the remote support code, I noticed that the idea
of the RemoteResult class is really disconnected to the current idea
of avocado.core.result.Result.

Also, it only serves the purpose of generating a dict with the state,
and it's only used once.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This is a prep work for making the Remote Runner an optional plugin.

By installing the Remote Runner through the usual ways (setup.py) the
dependencies will always be fullfilled, so this manual check is not
needed or desirable.

If users still want to check for the presence of this feature, they
should use standard Python pkg_resources for that.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The first line tells it all.  This logger instance is not used at all,
and is probably a leftover boilerplate.  Let's get rid of it.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Some setuptools versions on some code paths, such as when trying to
install extensions (what Python calls code that needs compilers) can
break when used in conjunction with pkg_resources.

The one observed issue is trying to access the
`pkg_resources.packaging` module which does not exist one some cases.

Let's pin the setuptools version on CI to avoid those nasty errors.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Add a notice to docs about configs in virtualenv.

Add a section to Configuration documentation about virtualenv.
Signed-off-by: NAndrei Stepanov <astepano@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  fail_on(): move internal implementation to avocado.core.decorators

The `avocado.core.decorators` module has been recently added with the
`skip*` family of decorators.  Still, we have `fail_on()`, also a
decorator, defined in `avocado.core.exceptions`.

For consistency, let's put them in the same module.  There are no
changes to users of the Avocado Test API.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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