docs/devel: rationalise unstable gitlab tests under FLAKY_TESTS
authorAlex Bennée <alex.bennee@linaro.org>
Fri, 1 Dec 2023 09:36:28 +0000 (09:36 +0000)
committerAlex Bennée <alex.bennee@linaro.org>
Fri, 1 Dec 2023 14:11:55 +0000 (14:11 +0000)
commit9b45cc9931866cedbe46d4372329074595267bfa
treee4300a993dde298e40fc6890090f7f67ee941ae7
parent5dcf6334ae1af158ec149794c3f35e459b98df5e
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>
13 files changed:
docs/devel/testing.rst
tests/avocado/boot_linux.py
tests/avocado/boot_linux_console.py
tests/avocado/intel_iommu.py
tests/avocado/linux_initrd.py
tests/avocado/machine_aspeed.py
tests/avocado/machine_mips_malta.py
tests/avocado/machine_rx_gdbsim.py
tests/avocado/machine_s390_ccw_virtio.py
tests/avocado/replay_kernel.py
tests/avocado/reverse_debugging.py
tests/avocado/smmu.py
tests/avocado/tuxrun_baselines.py