All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	qemu-devel@nongnu.org
Subject: [PATCH v3 0/3] tests/functional/asset: improve partial-download handling
Date: Wed, 12 Mar 2025 22:59:59 +1000	[thread overview]
Message-ID: <20250312130002.945508-1-npiggin@gmail.com> (raw)

v2 discussion:

https://lore.kernel.org/qemu-devel/20250312122559.944533-1-npiggin@gmail.com/T/#m9e610343e190d6e65148eb6c9d2e8f4eb8b857b8

Changes since v2:
- Fixed junk in patch 3.
- Add R-B.

Test results for functional-system-debian and -fedora can be seen here:
https://gitlab.com/npiggin/qemu/-/jobs/9387494994
https://gitlab.com/npiggin/qemu/-/jobs/9387495000

Including the short download and retry exceeded failures and skipping
the subtests without failing the entire job.

Thanks,
Nick

Nicholas Piggin (3):
  tests/functional/asset: Fail assert fetch when retries are exceeded
  tests/functional/asset: Verify downloaded size
  tests/functional/asset: Add AssetError exception class

 tests/functional/qemu_test/asset.py | 58 ++++++++++++++++++++++-------
 1 file changed, 44 insertions(+), 14 deletions(-)

-- 
2.47.1



             reply	other threads:[~2025-03-12 13:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 12:59 Nicholas Piggin [this message]
2025-03-12 13:00 ` [PATCH v3 1/3] tests/functional/asset: Fail assert fetch when retries are exceeded Nicholas Piggin
2025-03-12 13:00 ` [PATCH v3 2/3] tests/functional/asset: Verify downloaded size Nicholas Piggin
2025-03-12 13:00 ` [PATCH v3 3/3] tests/functional/asset: Add AssetError exception class Nicholas Piggin

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=20250312130002.945508-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=berrange@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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.