From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: "Eric Farman" <farman@linux.ibm.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Yoshinori Sato" <ysato@users.sourceforge.jp>,
"Cédric Le Goater" <clg@kaod.org>,
"Eric Auger" <eric.auger@redhat.com>,
qemu-arm@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Halil Pasic" <pasic@linux.ibm.com>,
"Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>,
"Aurelien Jarno" <aurelien@aurel32.net>,
qemu-s390x@nongnu.org, "Beraldo Leal" <bleal@redhat.com>,
"Joel Stanley" <joel@jms.id.au>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH 2/3] docs/devel: rationalise unstable gitlab tests under FLAKY_TESTS
Date: Thu, 30 Nov 2023 17:25:43 +0100 [thread overview]
Message-ID: <6678fa66-22f7-45f3-b83f-453faddd7d45@linaro.org> (raw)
In-Reply-To: <20231130153333.2424775-3-alex.bennee@linaro.org>
On 30/11/23 16:33, Alex Bennée wrote:
> 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.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> docs/devel/testing.rst | 31 +++++++++++++++---------
> tests/avocado/boot_linux.py | 8 +++---
> tests/avocado/boot_linux_console.py | 5 ++--
> tests/avocado/intel_iommu.py | 5 ++--
> tests/avocado/linux_initrd.py | 5 ++--
> tests/avocado/machine_aspeed.py | 8 +++---
> tests/avocado/machine_mips_malta.py | 8 +++---
> tests/avocado/machine_rx_gdbsim.py | 8 +++---
> tests/avocado/machine_s390_ccw_virtio.py | 2 +-
> tests/avocado/replay_kernel.py | 5 ++--
> tests/avocado/reverse_debugging.py | 14 +++++++----
> tests/avocado/smmu.py | 5 ++--
> tests/avocado/tuxrun_baselines.py | 4 +--
> 13 files changed, 67 insertions(+), 41 deletions(-)
> diff --git a/tests/avocado/boot_linux.py b/tests/avocado/boot_linux.py
> index be30dcbd58..9e9773e6e1 100644
> --- a/tests/avocado/boot_linux.py
> +++ b/tests/avocado/boot_linux.py
> @@ -12,7 +12,7 @@
>
> from avocado_qemu import LinuxTest, BUILD_DIR
>
> -from avocado import skipIf
> +from avocado import skipUnless
>
>
> class BootLinuxX8664(LinuxTest):
> @@ -93,7 +93,8 @@ class BootLinuxPPC64(LinuxTest):
>
> timeout = 360
>
> - @skipIf(os.getenv('GITLAB_CI'), 'Running on GitLab')
> + @skipUnless(os.getenv('QEMU_TEST_FLAKY_TESTS'), 'Test is unstable on GitLab')
Later we could move that to a @flakyTest decorator around QemuBaseTest.
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> +
> def test_pseries_tcg(self):
> """
> :avocado: tags=machine:pseries
next prev parent reply other threads:[~2023-11-30 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 15:33 [PATCH 0/3] final fixes for 8.2 Alex Bennée
2023-11-30 15:33 ` [PATCH 1/3] gdbstub: use a better signal when we halt for IO reasons Alex Bennée
2023-11-30 15:33 ` [PATCH 2/3] docs/devel: rationalise unstable gitlab tests under FLAKY_TESTS Alex Bennée
2023-11-30 16:06 ` Cédric Le Goater
2023-11-30 16:25 ` Philippe Mathieu-Daudé [this message]
2023-11-30 16:40 ` Peter Maydell
2023-11-30 16:59 ` Alex Bennée
2023-11-30 15:33 ` [PATCH 3/3] gitlab: add optional job to run flaky avocado tests Alex Bennée
2023-11-30 16:05 ` [PATCH 0/3] final fixes for 8.2 Richard Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6678fa66-22f7-45f3-b83f-453faddd7d45@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=andrew@codeconstruct.com.au \
--cc=aurelien@aurel32.net \
--cc=bleal@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@kaod.org \
--cc=crosa@redhat.com \
--cc=eric.auger@redhat.com \
--cc=farman@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=pasic@linux.ibm.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=ysato@users.sourceforge.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).