gnodet commented on PR #1909: URL: https://github.com/apache/maven-resolver/pull/1909#issuecomment-4649838352
The `IpcNamedLockFactoryIT.exclusiveAccess()` Windows CI failure has been investigated and a fix is up at #1910. **Root cause**: When the loser thread's lock acquisition times out in `doLockExclusively()`, the cleanup call `client.unlock(contextId)` could throw `RuntimeException` (e.g., due to Windows-specific socket behavior). This exception propagated out of `Access.run()` — which only catches `InterruptedException` — causing the thread to crash without calling `loser.countDown()`. The winner thread then waited on `loser.await()` forever, and Surefire killed the JVM at 25 seconds. A secondary issue: `client.unlock()` used `Long.MAX_VALUE` timeout, so if the server/receiver was unresponsive, the thread would hang indefinitely instead of failing fast. -- 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]
