[ 
https://issues.apache.org/jira/browse/HDDS-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-16750:
----------------------------------
    Labels: pull-request-available  (was: )

> 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
>              Labels: pull-request-available
>
> 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
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to