slachiewicz opened a new pull request, #1841:
URL: https://github.com/apache/maven-mvnd/pull/1841

   Part of #1839: a hung integration test now fails within 10 minutes instead 
of holding the job for up to six hours, and test daemons no longer outlive the 
run.
   
   - Timeouts: JUnit default 10 min, surefire and failsafe fork 1 h, 
`timeout-minutes: 60` on the CI jobs.
   - `killAll` falls back to `destroyForcibly()` and fails the class if a 
daemon survives, instead of printing and dropping the registry entry.
   - A shutdown hook runs `killAll` when `afterAll` does not, and each test 
class first kills processes started with its `-Dmvnd.daemonStorage` path, left 
by an earlier interrupted run.
   - Test daemons idle-expire after 10 minutes instead of 3 hours.
   
   Not included: failing fast when a build prompts or reads stdin. 
`InputStreamNativeIT` answers `RequestInput` itself and then calls 
`super.accept`, so a default reply would answer twice; the JUnit timeout covers 
that hang.
   
   Verified: a decoy JVM started with `ExecOutputTest`'s daemon storage path 
was killed when that test class started; `./mvnw clean verify -Dmrm=false` on 
macOS passed apart from a one-off `TypeDescriptionTest` artifact resolution 
failure, which passes on rerun.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to