Fix the pipeline failure about java - spring - ci

[rujche]

Description

• Link to failed pipeline: https://dev.azure.com/azure-sdk/internal/internal%20Team/_build/results?buildId=5991004&view=logs&j=ee4042b1-66fd-5231-28c8-44a1e7479e96&t=8f9d097e-d3c9-5e1f-bcee-22d0a0f45d92&l=509
• Screenshot of the failure:

  

The Spring CI pipeline job "Test ubuntu2404_121_NotFromSource_TestsOnly" intermittently hangs until the 60-minute pipeline timeout kills it. The failure is not deterministic — retrying the pipeline typically resolves it.

Root Cause Analysis

Investigation traced the hang to a JVM crash (EXCEPTION_ACCESS_VIOLATION in Class.getDeclaredConstructors0) occurring inside a Surefire forked JVM during Spring Boot test context creation. The crash happens under high concurrent class-loading pressure when:

Maven runs multiple modules in parallel (-T 1C)

Each module forks a JVM for testing (forkCount=1)
JUnit 5 parallel test execution is enabled (parallelizeTests=concurrent)
Mockito/byte-buddy dynamically generates proxy bytecode alongside Spring's ApplicationContext proxy creation
When the forked JVM crashes, Surefire reports "Corrupted channel by directly writing to native stream in forked JVM" but has no timeout configured — so Maven waits indefinitely for the dead process, causing the pipeline to hang until the Azure DevOps job timeout (60 minutes) kills the entire build.

Fix

Added 600 to the maven-surefire-plugin configuration in azure-client-sdk-parent. This gives each forked test JVM a 10-minute timeout. If a fork crashes or hangs, Surefire will detect the timeout, kill the process, and report a clear error instead of waiting indefinitely.

Verification

The 600-second (10-minute) timeout is generous enough that no legitimate test run should hit it — the full Spring autoconfigure module (1073 tests) completes in ~32 seconds locally.
When a fork does crash/hang, the pipeline will now fail fast with a descriptive timeout error and free the CI agent, rather than consuming the full 60-minute job timeout.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[rujche]

/azp run java - spring - ci

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[Copilot]

Pull request overview

Adds a timeout to Maven Surefire forked JVMs in the Azure SDK Java client parent POM to prevent CI jobs from hanging indefinitely when a forked test process crashes (e.g., corrupted channel / dead fork).

Changes:

• Configure maven-surefire-plugin with forkedProcessTimeoutInSeconds=600 in azure-client-sdk-parent to fail fast instead of waiting forever on a dead forked JVM.