All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: richard.henderson@linaro.org, qemu-devel@nongnu.org,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [PULL 2/3] tests/avocado: add timeout to the aspeed tests
Date: Tue, 16 Aug 2022 14:31:37 +0100	[thread overview]
Message-ID: <87mtc4b9d7.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA-+MtvsRJfpcjknT2FHkUO75AP_zySWBWi=KAAkMGdjnQ@mail.gmail.com>


Peter Maydell <peter.maydell@linaro.org> writes:

> On Tue, 16 Aug 2022 at 13:26, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> On some systems the test can hang. At least defining a timeout stops
>> it from hanging forever.
>
> Aha. Yeah, I've seen this test hang forever sometimes.
>
> Is there some place (in the superclass??) that we can put a
> default timeout that applies to *all* avocado tests, so we
> don't have the risk of forgetting it in a particular test?

It's a bit muddy. Most tests are sub-classed on LinuxTest which does
define a default timeout:

  class LinuxTest(LinuxSSHMixIn, QemuSystemTest):
      """Facilitates having a cloud-image Linux based available.

      For tests that indent to interact with guests, this is a better choice
      to start with than the more vanilla `QemuSystemTest` class.
      """

      timeout = 900
      distro = None
      username = 'root'
      password = 'password'
      smp = '2'
      memory = '1024'

However the aspeed tests are directly derived from QemuSystemTest.
Perhaps we should just move the timeout down to that or maybe
QemuBaseTest?

>
> -- PMM


-- 
Alex Bennée


  reply	other threads:[~2022-08-16 13:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 12:26 [PULL for 7.1 0/3] memory leak and testing tweaks Alex Bennée
2022-08-16 12:26 ` [PULL 1/3] linux-user: un-parent OBJECT(cpu) when closing thread Alex Bennée
2022-08-19  1:02   ` Richard Henderson
2022-08-19  8:37     ` Alex Bennée
2022-08-19 14:36       ` Richard Henderson
2022-08-16 12:26 ` [PULL 2/3] tests/avocado: add timeout to the aspeed tests Alex Bennée
2022-08-16 12:32   ` Peter Maydell
2022-08-16 13:31     ` Alex Bennée [this message]
2022-08-16 13:40       ` Peter Maydell
2022-08-16 12:26 ` [PULL 3/3] tests/avocado: apply a band aid to aspeed-evb login Alex Bennée
2022-08-16 15:58 ` [PULL for 7.1 0/3] memory leak and testing tweaks 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=87mtc4b9d7.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=crosa@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=wainersm@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.