This repository was archived by the owner on Mar 1, 2026. It is now read-only.
Fixes #4810 - Fix Jakarta REST TCK runner forked process timeout - #4811
Merged
mnriem merged 2 commits intoFeb 28, 2026
Conversation
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.
Problem
The Jakarta REST TCK runner uses the default Failsafe
forkedProcessTimeoutInSecondsvalue (30 seconds). Some server-side test classes take longer than 30 seconds for Piranha to start, deploy, and process the full test suite, causing the forked JVM to be killed mid-run and reporting spurious test failures.Solution
Set
forkedProcessTimeoutInSecondsto 120 in the REST TCK runnerpom.xml.Verification
Server-side TCK test classes that previously timed out now complete within the 120-second window.
Fixes #4810