From c8468d5ec9fb86912cc26ba7f9373c101af2f886 Mon Sep 17 00:00:00 2001
From: Maks Rafalko <maks.rafalko@gmail.com>
Date: Fri, 14 Aug 2026 15:46:32 +0200
Subject: [PATCH] chore(MSP-5160): disallow timeouts for Infection, setting
 `maxTimeouts` to 0
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Why?

See https://infection.github.io/2026/01/14/whats-new-in-0.32.3/

in a nutshell:

> Slow CI accumulation: You get timeouts to zero, the build is fast. You add a new feature - suddenly 20 new timeouts. Your CI now takes minutes longer. The worst part? There’s no way to know they exist without digging through logs.

> Hidden infinite loops: Some timeouts are simple performance hits on slow CI. Others are mutations that create infinite loops-the very test gaps Infection is supposed to find, now hidden among “acceptable” slowdowns.
---
 infection.json5 | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/infection.json5 b/infection.json5
index 47df5abb..71c6ffe7 100644
--- a/infection.json5
+++ b/infection.json5
@@ -7,5 +7,6 @@
   },
   "mutators": {
     "@default": true
-  }
+  },
+  "maxTimeouts": 0
 }