fix: increase waitForRunningContainer timeout from 120s to 300s

dkrizan · claude · dkrizan · commit d145c21171ed · 2026-04-16T20:17:07.000+02:00
The 120s timeout is too tight for CI runners, causing flaky E2E failures
when the Spring Boot container takes longer to start.

Co-Authored-By: Claude Opus 4.6 (1M context) &lt;noreply@anthropic.com&gt;
diff --git a/gradle/e2e.gradle b/gradle/e2e.gradle
@@ -78,7 +78,7 @@ tasks.register('waitForRunningContainer', Task) {
             }
         }
     }
-    timeout = Duration.ofSeconds(120)
+    timeout = Duration.ofSeconds(300)
 }
 
 tasks.register('installE2eDeps', Exec) {

Original file line number	Diff line number	Diff line change
`@@ -78,7 +78,7 @@ tasks.register('waitForRunningContainer', Task) {`
`78`	`78`	`}`
`79`	`79`	`}`
`80`	`80`	`}`
`81`		`- timeout = Duration.ofSeconds(120)`
	`81`	`+ timeout = Duration.ofSeconds(300)`
`82`	`82`	`}`
`83`	`83`
`84`	`84`	`tasks.register('installE2eDeps', Exec) {`