On 1/12/23 10:36, Alex Bennée wrote:
One problem with flaky tests is they often only fail under CI
conditions which makes it hard to debug. We add an optional allow_fail
job so developers can trigger the only the flaky tests in the CI
environment if they are debugging.
Message-Id: <20231130153333.2424775-4-alex.ben...@linaro.org>
Reviewed-by: Richard Henderson <richard.hender...@linaro.org>
Signed-off-by: Alex Bennée <alex.ben...@linaro.org>
---
v2
- add missing ppc64/aarch64 build
---
docs/devel/testing.rst | 15 ++++++------
.gitlab-ci.d/buildtest.yml | 30 ++++++++++++++++++++++++
This should be split, first add the 'flaky' infrastructure, then
mark tests as flaky, referencing the GitLab issue URL.
tests/avocado/boot_linux.py | 2 ++
tests/avocado/boot_linux_console.py | 1 +
tests/avocado/intel_iommu.py | 1 +
tests/avocado/linux_initrd.py | 2 ++
tests/avocado/machine_aspeed.py | 2 ++
tests/avocado/machine_mips_malta.py | 2 ++
tests/avocado/machine_rx_gdbsim.py | 2 ++
tests/avocado/machine_s390_ccw_virtio.py | 1 +
tests/avocado/replay_kernel.py | 2 ++
tests/avocado/reverse_debugging.py | 2 ++
tests/avocado/smmu.py | 1 +
tests/avocado/tuxrun_baselines.py | 1 +
14 files changed, 57 insertions(+), 7 deletions(-)
