slachiewicz opened a new issue, #2094: URL: https://github.com/apache/maven-resolver/issues/2094
### Affected version HEAD (observed on PR builds, 2026-08-30) ### Bug description `NamedLocksTrackingFileManagerTest`, via `TrackingFileManagerTestSupport`, fails intermittently on Linux and passes on rerun with no code change. ``` [ERROR] Tests run: 18, Failures: 1, Errors: 0, Skipped: 0 [ERROR] NamedLocksTrackingFileManagerTest>TrackingFileManagerTestSupport.testLock... ``` Observed on `Verify / ubuntu-latest jdk-21-zulu 4.0.0-rc-6` and, in a separate run, on `Verify / ubuntu-latest jdk-25-zulu 4.0.0-rc-6`. The excerpt is truncated because the runs were re-run afterwards, which replaced the logs. ### Why this looks like flakiness rather than a real failure The clearest evidence: one of the two branches failed this test, then passed it after a push whose **only** change was a Javadoc `@since` tag. A comment-only edit cannot affect file locking, so the same code produced both outcomes. Beyond that: - Neither pull request touches the named-locks or tracking-file-manager code. - Two different JDKs on the same OS, and green on every other matrix cell. - Both went green on rerun. ### Possibly related #2030 (closed) reported `IpcNamedLockFactoryIT` as flaky with a timeout, and wondered about thread safety. Different class, but the same area, so it may be worth checking whether a shared cause remains. I have not reproduced this locally; it did not occur in any local run I made. *This issue was created with AI assistance.* -- 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]
