Skip to content

Commit 85c2d99

Browse files
committed
test(daemon): raise the frontend announce deadline above the claim budget
The backpressure/EOF fixtures waited only 10s for the forked daemon to announce readiness, but the daemon's own startup includes the cohort-claim path whose internal budget is HOST_DAEMON_CLAIM_TIMEOUT_MS (12s). Under the 4-core oversubscription of CI runners a slow-but-legitimate startup blew past 10s and was SIGKILLed before it could announce, so daemon_frontend backpressure failed almost every ubuntu run while passing on fast machines. Raise the announce deadline to 30s, comfortably above the daemon's own worst-case budget. Verified: the backpressure failures no longer reproduce under a local CI-fidelity 4-core run. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
1 parent 5e23839 commit 85c2d99

1 file changed

Lines changed: 8 additions & 1 deletion

File tree

‎tests/test_daemon_frontend.c‎

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -786,8 +786,15 @@ static bool frontend_backpressure_run_isolated(bool maintenance) {
786786
(void)close(control_pipe[0]);
787787
}
788788
char announced_marker = '\0';
789+
/* The daemon child runs cbm_daemon_runtime_service_start before it can
790+
* announce, and that includes the cohort-claim path whose own internal
791+
* budget is HOST_DAEMON_CLAIM_TIMEOUT_MS (12s). An announce deadline
792+
* below that budget SIGKILLs a slow-but-legitimate startup — on
793+
* oversubscribed CI runners this fired every round (announced=0,
794+
* daemon_signal=9) while fast local machines never saw it. Keep the
795+
* deadline comfortably above the daemon's own worst-case budget. */
789796
bool announced_read = daemon > 0 && frontend_test_read_byte(ready_pipe[0], &announced_marker,
790-
cbm_now_ms() + 10000U);
797+
cbm_now_ms() + 30000U);
791798
bool announced = announced_read && announced_marker == 'R';
792799

793800
/* This raw runtime client intentionally owns no cohort lease. It is a

0 commit comments

Comments
 (0)