ppkarwasz commented on PR #3701: URL: https://github.com/apache/logging-log4j2/pull/3701#issuecomment-3005789414
Hi @kurtostfeld, No need to worry about the Windows build — we have a number of known flaky tests that tend to fail more frequently on Windows. This is largely due to how GitHub runners are provisioned: unlike Linux runners, which use containers, Windows runners are full virtual machines. They tend to be slower and more prone to timing-related issues, which makes race conditions more likely to surface. We track these flaky tests in [Develocity](https://develocity.apache.org/scans/tests?search.relativeStartTime=P90D&search.rootProjectNames=Apache%20Log4j%20BOM&search.tags=2.x&search.timeZoneId=Europe%2FWarsaw#) though we rarely find the time to fix them properly. If you're interested in digging into one of these and exploring what kind of synchronization might be missing, contributions are always welcome! Thanks again for your work on this PR. -- 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: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
