Before reporting an issue

• I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

ci

Describe the bug

WindowsServiceDistTest.testServiceLifecycle waits up to 60s for Keycloak to become accessible after starting as a Windows service. On slower runners, Keycloak startup can exceed 60s, causing the test to fail. The stop timeout (30s) is also tight on slow machines.

Version

26.6

Regression

• The issue is a regression

Expected behavior

Test passes, Keycloak becomes accessible after service start within the timeout.

Actual behavior

Test fails with: Keycloak should be accessible after service start ==> expected: <true> but was: <false>

How to Reproduce?

Run the test on a slower CI runner.

Anything else?

No response