V3.13.x test

[neil-xie]

What changed?

Why?

How did you test it?

Potential risks

Release notes

Documentation Changes

[gitar-bot]

CI failed: The CI build failed due to a likely timeout or resource exhaustion in the Dockerized test environment, resulting in a sudden worker shutdown.

Overview

Both 'Sticky On' and 'Sticky Off' unit test jobs failed with an abrupt [SHUTDOWN_WORKERS] event after approximately 30 minutes of execution. No specific test failures were captured, suggesting an infrastructure-level termination.

Failures

Gradle Build/Test Timeout (confidence: medium)

• Type: build
• Affected jobs: 73868520631, 73868520634
• Related to change: unclear
• Root cause: The build processes were forcefully shut down after 30+ minutes. This is consistent with a CI runner timeout or an Out-Of-Memory (OOM) event triggered by heavy memory requirements for Cassandra and Cadence containers within the Docker-compose stack.
• Suggested fix: Verify if the test suite duration has recently increased. If so, extend the job timeout. Alternatively, audit the resource limits in docker/github_actions/docker-compose.yml to ensure they do not exceed runner hardware capacities.

Summary

• Change-related failures: 0. The failure appears to be an environmental/infrastructure issue affecting the test suite execution.
• Infrastructure/flaky failures: 2. Both test jobs failed with a hard shutdown, likely due to resource contention or timeouts.
• Recommended action: Investigate the runner resource utilization during the Run unit test phase. If resource usage is high, consider optimizing the Docker environment configuration or increasing the runner size/timeout.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}