qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PULL 04/30] tests/avocado: add explicit timeout for s390 TCG tests


From: Thomas Huth
Subject: Re: [PULL 04/30] tests/avocado: add explicit timeout for s390 TCG tests
Date: Mon, 26 Sep 2022 18:27:28 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0

On 20/09/2022 19.15, Alex Bennée wrote:
We don't want to rely on the soon to be reduced default time. These
tests are still slow for something we want to run in CI though.

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20220914155950.804707-5-alex.bennee@linaro.org>

diff --git a/tests/avocado/boot_linux.py b/tests/avocado/boot_linux.py
index 67a24fe51c..4f07c27ac6 100644
--- a/tests/avocado/boot_linux.py
+++ b/tests/avocado/boot_linux.py
@@ -130,6 +130,8 @@ class BootLinuxS390X(LinuxTest):
      :avocado: tags=arch:s390x
      """
+ timeout = 240
+
      @skipIf(os.getenv('GITLAB_CI'), 'Running on GitLab')
      def test_s390_ccw_virtio_tcg(self):
          """

I've configured my QEMU with --enable-debug and thus this test takes much more time here, ca. 550 seconds, so it's currently failing...
Should we maybe scale the timeout values if --enable-debug is enabled?

 Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]