kriegaex commented on PR #210: URL: https://github.com/apache/maven-shade-plugin/pull/210#issuecomment-1903588421
I do not think it is pure chance that it happens in the new IT. Maybe, in some other part of Maven, at least in some versions, there are other concurrency issues we are hitting here by chance, just because we are testing this setup. If you run the build a few times and it does not re-occur, maybe the test is "just" flaky because of Maven or some situation on the GitHub server. If it happens more often, maybe we can try my initial solution with the reentrant lock and see if that one produces more stable results. Looking at the stack trace below the [error message in the Maven 3.6.3 JDK 8 Windows build](https://github.com/apache/maven-shade-plugin/actions/runs/7596727600/job/20718211260#step:8:8504), it seems as if the Maven `MultiThreadedBuilder` is involved. Maybe its resource management is suboptimal on a platform like Windows where open files are locked. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
