From bff624c75a6788b57ab4acdb175045d2cc97fc25 Mon Sep 17 00:00:00 2001 From: Martin Stein Date: Thu, 8 Oct 2020 18:19:34 +0200 Subject: [PATCH] test/entrypoint: extend timeout interval At least on some PIT-based platforms (x86_32 + pistachio/okl4/sel4), we run into trouble with the reworked timeout framework that now proccesses all pending timeouts before calling their handlers. This order change leads to a higher rate of handling of short periodic timeouts in the timer driver which can cause lower prioritized components to starve. Especially, if submitting signals (from timer to client) isn't cheap (as is the case on qemu + pistachio for example). Issue #3884 --- repos/base/src/test/entrypoint/main.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/repos/base/src/test/entrypoint/main.cc b/repos/base/src/test/entrypoint/main.cc index 536c82ab49..fe008c40cd 100644 --- a/repos/base/src/test/entrypoint/main.cc +++ b/repos/base/src/test/entrypoint/main.cc @@ -51,7 +51,7 @@ namespace Test_signal { struct Session_component; struct Entrypoint; - enum { TIMER_DURATION = 10'000ul }; + enum { TIMER_DURATION = 20'000ul }; } @@ -146,7 +146,7 @@ struct Main if (++rpc_count % 100 == 0) test_ep.sc.stats(); - if (rpc_count == 3'000) + if (rpc_count == 2'000) env.parent().exit(0); } };