Lucio Lelii d08fb4af4d test: evict finished executions from the in-memory cache more aggressively ... ExecutionsService's ExecutionObject cache only calls shutdown() (which tears down that execution's dedicated Executors.newFixedThreadPool) on eviction, gated by app.executions.cache.max-size (default 1000) and app.executions.cache.final-ttl-ms (default 30 minutes). The Spring test context - and its singleton ExecutionsService - is reused across the whole suite, and a full run finishes in well under 30 minutes with far fewer than 1000 executions, so none of that cleanup ever fires: every execution's thread pool stays alive simultaneously for the rest of the run. That's a plausible contributor to the loop-container tests occasionally missing their polling deadline under full-suite load (they pass reliably in isolation, where far fewer executions accumulate). Lowering both knobs for tests only keeps the live thread-pool count small throughout a run; eviction only ever targets already-finished executions (see evictIfNeeded/evictFinalStateByTtl), so this cannot disrupt an in-flight test.		2026-07-25 14:06:38 +02:00
..
main	feat: validate assistant flows with FlowExecutionValidator, raise repair budget to 2	2026-07-25 12:31:07 +02:00
test	test: evict finished executions from the in-memory cache more aggressively	2026-07-25 14:06:38 +02:00