This repository was archived by the owner on Jul 5, 2026. It is now read-only.
ci: fix Gradle test job being canceled due to no output timeout#153
Closed
circleci-app[bot] wants to merge 1 commit into
Closed
ci: fix Gradle test job being canceled due to no output timeout#153circleci-app[bot] wants to merge 1 commit into
circleci-app[bot] wants to merge 1 commit into
Conversation
Long-running parallel Gradle tests produce no console output while individual test suites execute, causing CircleCI to cancel the job after the default 10-minute no_output_timeout. Setting the timeout to 30m gives tests room to complete without being silently killed. AI-Generated: true
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
test-ubuntu-jdk21job ingradle_tests_workflowwas being canceled because long-running parallel Gradle tests produce no console output for extended periodsno_output_timeoutis 10 minutes — when Gradle runs tests in parallel, individual test suites can run silently for longer than that, causing the job to be killedno_output_timeout: 30mto the "Test with Gradle" step to give tests enough time to completeTest plan
test-ubuntu-jdk21job completes instead of being canceled in the next workflow runhttps://app.circleci.com/agents/gh/jmltoolkit/chat/f432f48f-b1a2-4d4d-a0ee-df3ac83111de