[
https://issues.apache.org/jira/browse/HDDS-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18126446#comment-18126446
]
Siyao Meng commented on HDDS-16750:
-----------------------------------
This recurred on master, not only on a fork branch.
Run: https://github.com/apache/ozone/actions/runs/38232863910/job/114762108370
(commit c3fa499ed7c, HDDS-9793), JDK 25.0.4.1, Surefire 3.5.2.
Recon reported 820 unit tests (0 failures, 0 errors, 32 skipped) and 39
integration tests (0 failures, 0 errors), but the ozone-recon module failed
with the same "ExecutionException Error occurred in starting fork, check output
in log" (SurefireBooterForkException at ForkStarter.fork(ForkStarter.java:577)).
The output log again has the native abort right after a test class finished
(here after TestReconStorageContainerManagerFacade):
{code}
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Aborted (core dumped)
{code}
The only dump file (2026-10-12T10-17-20_760-jvmRun1.dump) contains just the
Surefire PpidChecker call, with no recorded exit:
{code}
/bin/sh -c /usr/bin/ps -o etime,pid 2412
{code}
The root pom sets enableProcessChecker=all, so the ps poll by the checker may
be related, but that is not confirmed.
> Investigate Surefire fork failure in Recon CI with no reported test failures
> ----------------------------------------------------------------------------
>
> Key: HDDS-16750
> URL: https://issues.apache.org/jira/browse/HDDS-16750
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Huang Kuan Hao
> Assignee: Huang Kuan Hao
> Priority: Major
>
> The integration (recon) check failed on b41d78c5da (upstream base 402a0622fe)
> with JDK 25.0.4.1 and Surefire 3.5.2. Recon reported 790 unit tests (0
> failures, 0 errors, 32 skipped) and 39 integration tests (0 failures, 0
> errors), but Maven failed with a Surefire fork error.
> {code}
> ExecutionException Error occurred in starting fork, check output in log
> SurefireBooterForkException at ForkStarter.fork(ForkStarter.java:577)
> {code}
> The integration-recon artifact contains a JVM dump with PpidChecker,
> IOException: Stream closed, and IllegalStateException: error [STOPPED] to
> read process 2652. These are observed symptoms; their connection to the
> unsuccessful fork exit is not yet established. Investigate the fork failure
> and identify the affected test or process.
> HDDS-13307 addressed log scanning after successful test retries; this run
> reports an actual Surefire fork failure.
> CI:
> https://github.com/rich7420/ozone/actions/runs/37595249924/job/112711390698
> Artifact:
> https://github.com/rich7420/ozone/actions/runs/37595249924/artifacts/11472896153
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
