diff options
| author | Alex Bennée <alex.bennee@linaro.org> | 2023-12-01 09:36:28 +0000 |
|---|---|---|
| committer | Alex Bennée <alex.bennee@linaro.org> | 2023-12-01 14:11:55 +0000 |
| commit | 9b45cc9931866cedbe46d4372329074595267bfa (patch) | |
| tree | e4300a993dde298e40fc6890090f7f67ee941ae7 /tests/avocado/machine_s390_ccw_virtio.py | |
| parent | 5dcf6334ae1af158ec149794c3f35e459b98df5e (diff) | |
| download | qemu-9b45cc9931866cedbe46d4372329074595267bfa.zip qemu-9b45cc9931866cedbe46d4372329074595267bfa.tar.gz qemu-9b45cc9931866cedbe46d4372329074595267bfa.tar.bz2 | |
docs/devel: rationalise unstable gitlab tests under FLAKY_TESTS
It doesn't make sense to have two classes of flaky tests. While it may
take the constrained environment of CI to trigger failures easily it
doesn't mean they don't occasionally happen on developer machines. As
CI is the gating factor to passing there is no point developers
running the tests locally anyway unless they are trying to fix things.
While we are at it update the language in the docs to discourage the
QEMU_TEST_FLAKY_TESTS becoming a permanent solution.
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20231201093633.2551497-3-alex.bennee@linaro.org>
Diffstat (limited to 'tests/avocado/machine_s390_ccw_virtio.py')
| -rw-r--r-- | tests/avocado/machine_s390_ccw_virtio.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/avocado/machine_s390_ccw_virtio.py b/tests/avocado/machine_s390_ccw_virtio.py index ffd914d..61e75d8 100644 --- a/tests/avocado/machine_s390_ccw_virtio.py +++ b/tests/avocado/machine_s390_ccw_virtio.py @@ -12,7 +12,7 @@ import os import tempfile -from avocado import skipIf +from avocado import skipUnless from avocado_qemu import QemuSystemTest from avocado_qemu import exec_command_and_wait_for_pattern from avocado_qemu import wait_for_console_pattern |