From: Richard Henderson <richard.henderson@linaro.org>
To: Cleber Rosa <crosa@redhat.com>, Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Phil Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: avocado test failing INTERRUPTED for "Missing asset"
Date: Thu, 27 Jul 2023 17:02:49 -0700 [thread overview]
Message-ID: <270f0cfd-b57a-24b8-7c13-789bb9ee13ed@linaro.org> (raw)
In-Reply-To: <CA+bd_6LsQw3ao1KQk8Jk-VvAb9SZ1ioxSdBsghtNqJK-cnMRXA@mail.gmail.com>
On 7/27/23 12:08, Cleber Rosa wrote:
> Anyways, I'll look into, and report back on:
>
> 1. expanding avocado.Test.fetch_asset() with a timeout parameter
> 2. making sure the newer implementation for the requirement types used
> by QEMU respect a timeout (they don't need to be smaller than the
> test, because they run completely outside of the test).
>
> For now, are you OK with re-running those jobs if the servers stall
> the transfers? Or would you rather see a patch that changes the
> find_only parameter to True, so that if the pre-test attempt to
> download the asset fails, the transfer is never attempted during the
> test?
I would be perfectly happy with find_only. From your description that more-or-less
matches the behaviour of v103. I would also suggest that if the pre-test attempt fails,
trying again in just a few minutes during the test isn't likely to work either.
r~
prev parent reply other threads:[~2023-07-28 0:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 17:13 avocado test failing INTERRUPTED for "Missing asset" Peter Maydell
2023-07-26 7:33 ` Philippe Mathieu-Daudé
2023-07-26 9:07 ` Thomas Huth
2023-07-27 19:32 ` Cleber Rosa
2023-07-27 19:17 ` Cleber Rosa
2023-07-27 15:20 ` Cleber Rosa
2023-07-27 15:50 ` Peter Maydell
2023-07-27 19:08 ` Cleber Rosa
2023-07-27 19:57 ` Peter Maydell
2023-07-28 0:02 ` Richard Henderson [this message]
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=270f0cfd-b57a-24b8-7c13-789bb9ee13ed@linaro.org \
--to=richard.henderson@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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 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).