On Wed, Jul 19, 2023 at 03:26:11PM +0200, Thomas Huth wrote:
> On 17/07/2023 20.28, Daniel P. Berrangé wrote:
> > The pxe-test takes about 1 + 1/2 minutes in a --enable-debug
> > build. Bumping to 3 minutes will give more headroom.
> >
> > Signed-off-by: Daniel P. Berrangé <berra...@redhat.com>
> > ---
> > tests/qtest/meson.build | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/tests/qtest/meson.build b/tests/qtest/meson.build
> > index 1070c6dc64..c6da428dc5 100644
> > --- a/tests/qtest/meson.build
> > +++ b/tests/qtest/meson.build
> > @@ -4,6 +4,7 @@ slow_qtests = {
> > 'npcm7xx_pwm-test': 300,
> > 'qom-test' : 900,
> > 'test-hmp' : 240,
> > + 'pxe-test': 180,
> > }
>
> By the way, pxe-test uses the boot_sector_test() function, and that already
> uses a timeout of 600 seconds ... so we maybe should use the same (or even
> slightly higher) timeout value here?
Your original change setting that 600 limit says:
If QEMU has been compiled with the flags --enable-tcg-interpreter and
--enable-debug, the guest is running incredibly slow. The pxe boot test
can take up to 400 seconds when testing the pseries ppc64 machine.
so yeah, we need to set the timeout for pxe-test to 600 seconds
too. I guess likewise for other tests using boot_sector_test()
function too.
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 :|
