This issue was generated automatically by Claude Code (Anthropic's AI coding agent) running a scheduled CI-triage routine on behalf of @FrankChen021. Analysis and suggested fixes are AI-produced; please verify before acting on them.
Status: Open: no fix PR
Subject: EmbeddedSecureJdbcDriverTest class run (jdbc-driver, unit tests (25, E*,G*,F*))
Failures: 1 · First seen: 2026-10-09 · Last seen: 2026-10-09
Root cause
About 15 s after EmbeddedSecureJdbcDriverTest started its embedded cluster, the surefire fork exited with code 1 and no test result, so surefire reported "The forked VM terminated without properly saying goodbye". A JVM crash or an OOM would give a different exit code. Code 1 matches the in-process System.exit(1) paths that embedded servers can reach: the Curator unhandled-error listener in CuratorModule and CuratorDruidLeaderSelector.notLeader(). All embedded servers share the surefire JVM, so either path kills the whole fork. The commit (#20524, ZooKeeper 3.8.6 → 3.8.7) is probably not the cause, because the next two master commits also use 3.8.7 and the job passed on both.
Suggested fix
In the embedded-test harness, replace the JVM-exiting actions with ones that fail the test instead: inject CuratorModule's exitAction, and route CuratorDruidLeaderSelector's exit through an injectable hook. The root error then appears as a test failure with server logs. Until then, check the *.dumpstream in the run's unit-test-reports-jdk25-* artifact to confirm which path ran.
Occurrences
Failed push-triggered master jobs only. The daily triage routine adds one row per new failed job.
| Date |
Commit |
Job |
Failure log |
Detail |
Reported in |
| 2026-10-09 |
9a79249 (#20524) |
unit tests / unit tests(main) (25, E*,G*,F*) / test-jdk25-[E*,G*,F*] |
job 113693242067 |
surefire fork exited with code 1 during EmbeddedSecureJdbcDriverTest cluster startup; 0 tests reported, no retry |
|
This issue was generated automatically by Claude Code (Anthropic's AI coding agent) running a scheduled CI-triage routine on behalf of @FrankChen021. Analysis and suggested fixes are AI-produced; please verify before acting on them.
Status: Open: no fix PR
Subject:
EmbeddedSecureJdbcDriverTestclass run (jdbc-driver,unit tests (25, E*,G*,F*))Failures: 1 · First seen: 2026-10-09 · Last seen: 2026-10-09
Root cause
About 15 s after
EmbeddedSecureJdbcDriverTeststarted its embedded cluster, the surefire fork exited with code 1 and no test result, so surefire reported "The forked VM terminated without properly saying goodbye". A JVM crash or an OOM would give a different exit code. Code 1 matches the in-processSystem.exit(1)paths that embedded servers can reach: the Curator unhandled-error listener inCuratorModuleandCuratorDruidLeaderSelector.notLeader(). All embedded servers share the surefire JVM, so either path kills the whole fork. The commit (#20524, ZooKeeper 3.8.6 → 3.8.7) is probably not the cause, because the next two master commits also use 3.8.7 and the job passed on both.Suggested fix
In the embedded-test harness, replace the JVM-exiting actions with ones that fail the test instead: inject
CuratorModule'sexitAction, and routeCuratorDruidLeaderSelector's exit through an injectable hook. The root error then appears as a test failure with server logs. Until then, check the*.dumpstreamin the run'sunit-test-reports-jdk25-*artifact to confirm which path ran.Occurrences
Failed push-triggered master jobs only. The daily triage routine adds one row per new failed job.
unit tests / unit tests(main) (25, E*,G*,F*) / test-jdk25-[E*,G*,F*]EmbeddedSecureJdbcDriverTestcluster startup; 0 tests reported, no retry