On Mon, Jul 01, 2024, Aaron Lewis wrote: > This test can take over 10 seconds to run on IvyBridge in debug. > Increase the timeout to give this test the time it needs to complete. Heh, there's a pretty big gap between 10 seconds and 100 seconds. Can we tighten the timeout, e.g. to 30 seconds, without risking false failures on IVB? > Signed-off-by: Aaron Lewis <aaronlewis@xxxxxxxxxx> > --- > x86/unittests.cfg | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/x86/unittests.cfg b/x86/unittests.cfg > index 7c1691a988621..51c063d248e19 100644 > --- a/x86/unittests.cfg > +++ b/x86/unittests.cfg > @@ -349,7 +349,7 @@ file = vmx.flat > extra_params = -cpu max,+vmx -append "apic_reg_virt_test virt_x2apic_mode_test vmx_basic_vid_test vmx_eoi_virt_test" > arch = x86_64 > groups = vmx > -timeout = 10 > +timeout = 100 > > [vmx_posted_intr_test] > file = vmx.flat > -- > 2.45.2.803.g4e1b14247a-goog >
