You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Log server output and thread dump when the test framework server fails to start #55363
When the test framework's DistributionKeycloakServer fails to start or does not become ready within the timeout, the test only fails with Server did not become ready within 120 seconds, and the managed server is killed without any further information. The managed server's output is only forwarded at WARN level and above, so the CI log contains nothing that explains why the server did not start. This was seen in the Windows CI job (Java Distribution IT/UT, windows-latest, temurin 27), where JavaKeystoreKeyProviderTest failed because the server did not become ready, while the rerun of the same test started the server in about 25 seconds.
On a failed startup, and before the server process is killed, the test framework should log a report with the state of the process and its child processes, all output of the server since it was started (including INFO level and stderr), and a thread dump of each running Java process. The thread dump should be taken with jcmd, as sending a signal to trigger it is not available on Windows.
Activity
Log server output and thread dump when the test framework server fail…