From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>, alex.bennee@linaro.org
Subject: Re: [PATCH] acceptance: update asset hashes for the Bionic aarch64 installer
Date: Mon, 10 Aug 2020 11:40:16 +0200 [thread overview]
Message-ID: <2eef5241-c3fb-79bb-59a8-271a6fadd5e7@redhat.com> (raw)
In-Reply-To: <20200809223741.56570-1-pbonzini@redhat.com>
On 8/10/20 12:37 AM, Paolo Bonzini wrote:
> The kernel and initrd hashes seem to have changed for the Bionic
> aarch64 installer, causing BootLinuxConsole.test_aarch64_xlnx_versal_virt
> to fail. Correct them based on the latest.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> tests/acceptance/boot_linux_console.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/acceptance/boot_linux_console.py b/tests/acceptance/boot_linux_console.py
> index 73cc69c499..1fcd154a7c 100644
> --- a/tests/acceptance/boot_linux_console.py
> +++ b/tests/acceptance/boot_linux_console.py
> @@ -338,13 +338,13 @@ class BootLinuxConsole(LinuxKernelTest):
> kernel_url = ('http://ports.ubuntu.com/ubuntu-ports/dists/'
> 'bionic-updates/main/installer-arm64/current/images/'
> 'netboot/ubuntu-installer/arm64/linux')
> - kernel_hash = '5bfc54cf7ed8157d93f6e5b0241e727b6dc22c50'
> + kernel_hash = 'd6d17cc43d14f503493bd38e8277870f2b79132e'
> kernel_path = self.fetch_asset(kernel_url, asset_hash=kernel_hash)
>
> initrd_url = ('http://ports.ubuntu.com/ubuntu-ports/dists/'
> 'bionic-updates/main/installer-arm64/current/images/'
> 'netboot/ubuntu-installer/arm64/initrd.gz')
> - initrd_hash = 'd385d3e88d53e2004c5d43cbe668b458a094f772'
> + initrd_hash = '7363cd9211b572add76a68df086be24545813b5f'
> initrd_path = self.fetch_asset(initrd_url, asset_hash=initrd_hash)
>
> self.vm.set_console()
>
I haven't noticed that because I have these files in the Avocado cache.
The only way to detect such problems is blowing the cache... I certainly
don't want to do that daily. OTOH a developer starting to use the CI or
Avocado locally will hit the problem.
I was thinking about running a job with empty cache for each tags.
Maybe it is safer to do that on a weekly basis a least?
Regards,
Phil.
prev parent reply other threads:[~2020-08-10 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 22:37 [PATCH] acceptance: update asset hashes for the Bionic aarch64 installer Paolo Bonzini
2020-08-10 9:06 ` Philippe Mathieu-Daudé
2020-08-10 9:24 ` Paolo Bonzini
2020-08-10 9:35 ` Philippe Mathieu-Daudé
2020-08-10 11:13 ` Paolo Bonzini
2020-08-10 9:40 ` Philippe Mathieu-Daudé [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=2eef5241-c3fb-79bb-59a8-271a6fadd5e7@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--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 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).