On Fri, Jul 26, 2024 at 09:44:28AM -0400, Cleber Rosa wrote:
> Based on many runs, the average run time for these 4 tests is around
> 250 seconds, with 320 seconds being the ceiling. In any way, the
> default 120 seconds timeout is inappropriate in my experience.
> Let's increase the timeout so these tests get a chance to completion.
A high watermark of over 5 minutes is pretty long for a test.
Looking at the test I see it runs
self.ssh_command('dnf -y install numactl-devel')
but then never actually uses the installed package.
I expect that most of the wallclock time here is coming from having
dnf download all the repodata, 4 times over.
If the intention was to test networking, then replace this with
something that doesn't have to download 100's of MB of data, then
see what kind of running time we get before increasing any timeout.
> Signed-off-by: Cleber Rosa <crosa@xxxxxxxxxx>
> ---
> tests/avocado/intel_iommu.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/avocado/intel_iommu.py b/tests/avocado/intel_iommu.py
> index 008f214397..9e7965c5df 100644
> --- a/tests/avocado/intel_iommu.py
> +++ b/tests/avocado/intel_iommu.py
> @@ -25,6 +25,8 @@ class IntelIOMMU(LinuxTest):
> :avocado: tags=flaky
> """
>
> + timeout = 360
> +
> IOMMU_ADDON = ',iommu_platform=on,disable-modern=off,disable-legacy=on'
> kernel_path = None
> initrd_path = None
> --
> 2.45.2
>
>
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 :|
