From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel@nongnu.org,
"Leif Lindholm" <leif.lindholm@oss.qualcomm.com>,
qemu-arm@nongnu.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Radoslaw Biernacki" <rad@semihalf.com>
Subject: Re: [PATCH 2/2] tests/functional: migrate sbsa_ref test images
Date: Thu, 29 Jan 2026 12:13:23 +0000 [thread overview]
Message-ID: <875x8kaa70.fsf@draig.linaro.org> (raw)
In-Reply-To: <c2e17000-e34e-4244-a377-ffd37627aba0@linaro.org> (Pierrick Bouvier's message of "Wed, 28 Jan 2026 16:53:20 -0800")
Pierrick Bouvier <pierrick.bouvier@linaro.org> writes:
> On 1/28/26 8:25 AM, Peter Maydell wrote:
>> On Wed, 28 Jan 2026 at 10:58, Alex Bennée <alex.bennee@linaro.org> wrote:
>>>
>>> As the builds in codelinaro.org are going away migrate the binaries to
>>> share.linaro.org. As the hotlinks don't encode the filename we need to
>>> explicitly tell uncompress how to handle the files.
>>>
>>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>>
>>> @@ -54,15 +54,11 @@ class Aarch64SbsarefMachine(QemuSystemTest):
>>>
>>> timeout = 180
>>>
>>> - ASSET_FLASH0 = Asset(
>>> - ('https://artifacts.codelinaro.org/artifactory/linaro-419-sbsa-ref/'
>>> - '20241122-189881/edk2/SBSA_FLASH0.fd.xz'),
>>> - '76eb89d42eebe324e4395329f47447cda9ac920aabcf99aca85424609c3384a5')
>>> + ASSET_FLASH0 = Asset('https://share.linaro.org/downloadFile?id=kyoMLGC9zXa4oA7',
>>> + '76eb89d42eebe324e4395329f47447cda9ac920aabcf99aca85424609c3384a5')
>>>
>>> - ASSET_FLASH1 = Asset(
>>> - ('https://artifacts.codelinaro.org/artifactory/linaro-419-sbsa-ref/'
>>> - '20241122-189881/edk2/SBSA_FLASH1.fd.xz'),
>>> - 'f850f243bd8dbd49c51e061e0f79f1697546938f454aeb59ab7d93e5f0d412fc')
>>> + ASSET_FLASH1 = Asset('https://share.linaro.org/downloadFile?id=Dj1HRXnDnKtU6Nj',
>>> + 'f850f243bd8dbd49c51e061e0f79f1697546938f454aeb59ab7d93e5f0d412fc')
>> Is there really no way to have a human readable filename here? I
>> know what
>> edk2/SBSA_FLASH1.fd.xz is; I have no idea what
>> f850f243bd8dbd49c51e061e0f79f1697546938f454aeb59ab7d93e5f0d412fc is
>> going to be.
>>
>
> Hosting on GitHub/GitLab as a release file?
> Or anywhere else than share.linaro.org and that has names instead of
> hashes for url (i.e. not Google drive).
If you can setup a build pipeline that generates releases got for it.
However for it's faults at least we have control of share.linaro.org - I
have no idea what the policy for hosting binaries on github is. I'm
almost sure it violates some policy otherwise people would spam github
for cheap hosting.
The tool does actually know the name in the schema:
Name string
example: Test File.jpg
The filename. Will be 'Encrypted file' for end-to-end encrypted files
I note it is currently running 1.0 - we could see if the later versions
allow it.
>> If we can't have useful filenames, can we have comments saying what
>> the filenames
>> would be if we could have them?
>> thanks
>> -- PMM
>>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2026-01-29 12:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 10:58 [PATCH 0/2] testing/next: current patches (docker, test asset migration) Alex Bennée
2026-01-28 10:58 ` [PATCH 1/2] tests/docker: rename wasm cross container Alex Bennée
2026-01-29 15:02 ` Daniel P. Berrangé
2026-01-28 10:58 ` [PATCH 2/2] tests/functional: migrate sbsa_ref test images Alex Bennée
2026-01-28 15:58 ` Pierrick Bouvier
2026-01-28 16:25 ` Peter Maydell
2026-01-28 17:24 ` Alex Bennée
2026-01-28 18:14 ` Philippe Mathieu-Daudé
2026-01-29 0:53 ` Pierrick Bouvier
2026-01-29 12:13 ` Alex Bennée [this message]
2026-01-28 16:53 ` Philippe Mathieu-Daudé
2026-02-02 13:18 ` Michael Tokarev
2026-02-02 14:13 ` Alex Bennée
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=875x8kaa70.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=leif.lindholm@oss.qualcomm.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rad@semihalf.com \
--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.