diff options
author | Cleber Rosa <crosa@redhat.com> | 2019-03-12 13:18:09 -0400 |
---|---|---|
committer | Eduardo Habkost <ehabkost@redhat.com> | 2019-05-02 21:33:26 -0300 |
commit | b194713f94b286fd1f2bccace45cb5b25316e232 (patch) | |
tree | 0a1b55135af11efd3067354b4b6399f37cab4b64 /docs | |
parent | 2c44d68f2b004e41136996fef0e4122e6507ba90 (diff) | |
download | qemu-b194713f94b286fd1f2bccace45cb5b25316e232.zip qemu-b194713f94b286fd1f2bccace45cb5b25316e232.tar.gz qemu-b194713f94b286fd1f2bccace45cb5b25316e232.tar.bz2 |
tests/acceptance: use "arch:" tag to filter target specific tests
Currently, some tests contains target architecture information, in the
form of a "x86_64" tag. But that tag is not respected in the default
execution, that is, "make check-acceptance" doesn't do anything with
it.
That said, even the target architecture handling currently present in
the "avocado_qemu.Test" class is pretty limited. For instance, by
default, it chooses a target based on the host architecture.
Because the original implementation of the tags feature in Avocado did
not include any time of namespace or "key:val" mechanism, no tag has
relation to another tag. The new implementation of the tags feature
from version 67.0 onwards, allows "key:val" tags, and because of that,
a test can be classified with a tag in a given key. For instance, the
new proposed version of the "boot_linux_console.py" test, which
downloads and attempts to run a x86_64 kernel, is now tagged as:
:avocado: tags=arch:x86_64
This means that it can be filtered (out) when no x86_64 target is
available. At the same time, tests that don't have a "arch:" tag,
will not be filtered out.
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Message-Id: <20190312171824.5134-6-crosa@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions