[education/rkward] rkward/autotests: Be more lenient regarding test timing

Thomas Friedrichsmeier null at kde.org
Sun Sep 14 19:26:16 BST 2025


Git commit c4cf96c282b7af81995a61d5962cbeb0faa73202 by Thomas Friedrichsmeier.
Committed on 13/09/2025 at 14:24.
Pushed by tfry into branch 'master'.

Be more lenient regarding test timing

M  +2    -3    rkward/autotests/core_test.cpp

https://invent.kde.org/education/rkward/-/commit/c4cf96c282b7af81995a61d5962cbeb0faa73202

diff --git a/rkward/autotests/core_test.cpp b/rkward/autotests/core_test.cpp
index 5ebe3b455..f0221f6e2 100644
--- a/rkward/autotests/core_test.cpp
+++ b/rkward/autotests/core_test.cpp
@@ -511,10 +511,9 @@ class RKWardCoreTest : public QObject {
 		runCommandWithTimeout(c, nullptr, [this](RCommand *command) {
 			// QVERIFY(command->wasCanceled()); we're currenly mis-detecting that, which is not a real-world problem, however.
 			// The real test is the command neither times out (below), nor prints "after" (above)
-			QVERIFY(command->failed());
-		});
+			QVERIFY(command->failed()); }, 2000);
 		RInterface::issueCommand(QStringLiteral("dev.off()"), RCommand::User);
-		waitForAllFinished();
+		waitForAllFinished(2000);
 	}
 
 	void priorityCommandTest() {



More information about the rkward-tracker mailing list