qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: eric.auger@redhat.com, "Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-devel@nongnu.org
Cc: Wainer dos Santos Moschetta <wainersm@redhat.com>,
	Beraldo Leal <bleal@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH] tests/avocado/intel_iommu: Add asset hashes to avoid warnings
Date: Wed, 15 Nov 2023 07:20:13 +0100	[thread overview]
Message-ID: <ff6f2d1f-dc7a-408c-a6d8-19e5fec9fea6@redhat.com> (raw)
In-Reply-To: <5f09ba2a-3e62-454a-8665-0f80508b5168@redhat.com>

On 14/11/2023 21.42, Eric Auger wrote:
> Hi Thomas,
> 
> On 11/14/23 15:35, Thomas Huth wrote:
>> The intel_iommu test is currently succeeding with annoying warnings.
> nit: you may have precised the nature of the warning or quotes

The annoying warnings look like this (in the summary):

  (031/174) tests/avocado/intel_iommu.py:IntelIOMMU.test_intel_iommu: WARN: 
Test passed but there were warnings during execution. Check the log for 
details. (67.87 s)
  (032/174) tests/avocado/intel_iommu.py:IntelIOMMU.test_intel_iommu_strict: 
WARN: Test passed but there were warnings during execution. Check the log 
for details. (55.83 s)
  (033/174) 
tests/avocado/intel_iommu.py:IntelIOMMU.test_intel_iommu_strict_cm: WARN: 
Test passed but there were warnings during execution. Check the log for 
details. (56.01 s)
  (034/174) tests/avocado/intel_iommu.py:IntelIOMMU.test_intel_iommu_pt: 
WARN: Test passed but there were warnings during execution. Check the log 
for details. (54.06 s)

... not too helpful to quote them in the commit log, I guess...

>> Add the proper asset hashes to avoid those.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>   tests/avocado/intel_iommu.py | 6 ++++--
>>   1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/tests/avocado/intel_iommu.py b/tests/avocado/intel_iommu.py
>> index 474d62f6bf..77635ab56c 100644
>> --- a/tests/avocado/intel_iommu.py
>> +++ b/tests/avocado/intel_iommu.py
>> @@ -54,9 +54,11 @@ def common_vm_setup(self, custom_kernel=None):
>>               return
>>   
>>           kernel_url = self.distro.pxeboot_url + 'vmlinuz'
>> +        kernel_hash = '5b6f6876e1b5bda314f93893271da0d5777b1f3c'
>>           initrd_url = self.distro.pxeboot_url + 'initrd.img'
>> -        self.kernel_path = self.fetch_asset(kernel_url)
>> -        self.initrd_path = self.fetch_asset(initrd_url)
>> +        initrd_hash = 'dd0340a1b39bd28f88532babd4581c67649ec5b1'
>> +        self.kernel_path = self.fetch_asset(kernel_url, asset_hash=kernel_hash)
>> +        self.initrd_path = self.fetch_asset(initrd_url, asset_hash=initrd_hash)
>>   
>>       def run_and_check(self):
>>           if self.kernel_path:
> Besides,
> Reviewed-by: Eric Auger <eric.auger@redhat.com>

Thanks!

  Thomas



  reply	other threads:[~2023-11-15  6:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 14:35 [PATCH] tests/avocado/intel_iommu: Add asset hashes to avoid warnings Thomas Huth
2023-11-14 20:42 ` Eric Auger
2023-11-15  6:20   ` Thomas Huth [this message]
2023-11-15  8:31     ` Eric Auger

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=ff6f2d1f-dc7a-408c-a6d8-19e5fec9fea6@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=crosa@redhat.com \
    --cc=eric.auger@redhat.com \
    --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).