apache / apache/maven-surefire
[SUREFIRE-1929] forkedProcessTimeoutInSeconds is controlled by the plugin process and the sub-process ends gracefully. The forked process should be able to timeout itself if the MasterProcessChannelProcessorFactory.connect() fails or hangs.
Open
bug
priority:minor
- Dominant language
- Java
- Stars
- 461
- Forks
- 588
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 19
Description
**[Tibor Digana](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tibor17)** opened **[SUREFIRE-1929](https://issues.apache.org/jira/browse/SUREFIRE-1929?redirect=false)** and commented
---
**Affects:** 3.0.0-M5
Contributor guide
Research direction
Start by tracing the forked process and the MasterProcessChannelProcessorFactory.connect() entry point, then examine how forkedProcessTimeoutInSeconds is currently controlled by the plugin process. Confirm the behavior when connect() fails or hangs, and consider the work complete when the forked process can enforce its own timeout in that situation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100