From dedf9cf264656c7ce396fb66b69e3c8fcfd458c4 Mon Sep 17 00:00:00 2001 From: Laurent Pinchart Date: Wed, 24 Apr 2024 22:51:38 +0300 Subject: test: fence: Increase timeout for fence test On slower machines, a 1s timeout to capture frames with vimc can be too short and cause test failures. Make the timeout proportional to the number of frames expected to be captured, using a conservative low estimate of the frame rate at 2fps. By itself, that change could increase the test time quite substantially on fast platforms, so break from the capture loop as soon as we capture enough frames. Signed-off-by: Laurent Pinchart Reviewed-by: Daniel Scally Reviewed-by: Kieran Bingham --- test/fence.cpp | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/test/fence.cpp b/test/fence.cpp index a8fba728..8095b228 100644 --- a/test/fence.cpp +++ b/test/fence.cpp @@ -327,10 +327,14 @@ int FenceTest::run() Timer fenceTimer; fenceTimer.timeout.connect(this, &FenceTest::signalFence); - /* Loop for one second. */ + /* + * Loop long enough for all requests to complete, allowing 500ms per + * request. + */ Timer timer; - timer.start(1000ms); - while (timer.isRunning() && expectedCompletionResult_) { + timer.start(500ms * (signalledRequestId_ + 1)); + while (timer.isRunning() && expectedCompletionResult_ && + completedRequestId_ <= signalledRequestId_ + 1) { if (completedRequestId_ == signalledRequestId_ - 1 && setFence_) /* * The request just before signalledRequestId_ has just -- cgit v1.2.1