From 18b317cbb259f55ff737e7d38b622fe3cf16c005 Mon Sep 17 00:00:00 2001 From: ivanovac Date: Tue, 21 Apr 2026 14:04:09 +0300 Subject: [PATCH] Fix JRuby timeout to respect CF platform limit (180s max) PR #1140 increased the timeout to 300s, but the CF platform has a configured maximum of 180s (cc.maximum_health_check_timeout: 180). This causes deployment failures: 'health_check_timeout Maximum exceeded: max 180s' The test polling timeout increase (3min -> 5min) from PR #1140 is correct and remains in place. That gives the test sufficient time to wait for JRuby warmup after the health check passes. This fix reverts only the manifest.yml timeout back to 180s while keeping the test timeout at 5 minutes, which achieves the goal of reducing flaky failures without violating platform constraints. Fixes: #1140 (partial revert of manifest.yml change) --- fixtures/default/sinatra_jruby/manifest.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fixtures/default/sinatra_jruby/manifest.yml b/fixtures/default/sinatra_jruby/manifest.yml index 438534913..c03c2e7dd 100644 --- a/fixtures/default/sinatra_jruby/manifest.yml +++ b/fixtures/default/sinatra_jruby/manifest.yml @@ -2,4 +2,4 @@ applications: - name: sinatra_jruby_web_app health-check-type: process - timeout: 300 + timeout: 180