qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: avocado-devel@redhat.com, "Cleber Rosa" <crosa@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Did Avocado assets hashing system changed?
Date: Wed, 13 Sep 2023 16:20:39 +0100	[thread overview]
Message-ID: <ZQHTR9UIdViemD2k@redhat.com> (raw)
In-Reply-To: <4169f3e6-96b8-81af-ef09-35629b34caa7@linaro.org>

On Wed, Sep 13, 2023 at 04:17:24PM +0200, Philippe Mathieu-Daudé wrote:
> Hi,
> 
> We are trying to figure out why old assets saved in our Avocado
> cache (which we populate in our various CI jobs) isn't used
> anymore.
> 
> Trying to reproduce locally, I see for example:
> 
> 2023-09-13 14:39:18,834 test             L0520 INFO | START
> 14-tests/avocado/machine_mips_malta.py:MaltaMachine.test_mipsel_malta_yamon
> 2023-09-13 14:39:18,834 test             L0205 DEBUG| DATA
> (filename=output.expected) => NOT FOUND (data sources: variant, test, file)
> 2023-09-13 14:39:18,861 asset            L0339 INFO | Asset not in cache,
> fetching it.
> 2023-09-13 14:39:18,862 download         L0067 INFO | Fetching
> http://www.imgtec.com/tools/mips-tools/downloads/yamon/yamon-bin-02.22.zip
> -> /home/philippe.mathieu-daude/avocado/data/cache/by_location/70c32932b7794b6b37a5040a8808ac943699b944/yamon-bin-02.22.zip.csi3gk2v
> 2023-09-13 14:39:18,940 asset            L0144 INFO | Temporary asset file
> unavailable due to failed download attempt.
> 2023-09-13 14:39:18,940 asset            L0378 ERROR| HTTPError: HTTP Error
> 403: Forbidden
> 
> I remember this test used to pass last year, so checking the file I
> can see:
> 
> $ find ~/avocado/data/ -name yamon-bin-02.22.zip\* -ls
>   1489611   6629 -rw-r--r--   1 philmd primary   6776580 Dec 30  2022 /home/philmd/avocado/data/cache/by_location/c1961386ba52f06c6005b48cd32195a371152769/yamon-bin-02.22.zip
>   1489613      1 -rw-r--r--   1 philmd primary        46 Dec 30  2022 /home/philmd/avocado/data/cache/by_location/c1961386ba52f06c6005b48cd32195a371152769/yamon-bin-02.22.zip-CHECKSUM
> 
> But the hash is different... Looking at QEMU git history we haven't
> changed the URL in tests/avocado/machine_mips_malta.py, so I wonder,
> did Avocado changed its asset hashing during the last year?

How can it have changed when we've been pinned to avocado 88.1 for
ages now, not consuming new versions ?

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2023-09-13 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 14:17 Did Avocado assets hashing system changed? Philippe Mathieu-Daudé
2023-09-13 15:20 ` Daniel P. Berrangé [this message]
2023-09-13 15:40   ` Thomas Huth
2023-09-13 15:50     ` Daniel P. Berrangé

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=ZQHTR9UIdViemD2k@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=avocado-devel@redhat.com \
    --cc=crosa@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 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).