logback / LOGBACK-1668 [Open] RollingCalendarTest#testCollisionFreeness failing on "my machine" ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1668 ============================== Issue created ------------------------------ Bertrand Renuart created this issue on 22/Aug/22 11:00 AM Summary: RollingCalendarTest#testCollisionFreeness failing on "my machine" Issue Type: Bug Affects Versions: 1.3.0-beta0 Assignee: Logback dev list Components: logback-core Created: 22/Aug/22 11:00 AM Priority: Major Reporter: Bertrand Renuart Description: RollingCalendarTest#testCollisionFreeness is always failing when executed on "my machine". {code:java} Failed tests: RollingCalendarTest.testCollisionFreenes:187->checkCollisionFreeness:200 {code} I initially thought it was caused by some particularities of my dev environment until I noticed it also happen sometimes for MacOS Github builds. Oddly enough, it does not happen all the time in Github whereas this test never succeeds on my machine. I tried to find the root cause of the issue but honestly I don't understand what this test is actually doing :-( I ran the test with the following JDK versions and it failed every time: {code} openjdk version "11.0.15" 2022-04-19 LTS OpenJDK Runtime Environment Zulu11.56+19-CA (build 11.0.15+10-LTS) OpenJDK 64-Bit Server VM Zulu11.56+19-CA (build 11.0.15+10-LTS, mixed mode) openjdk version "17.0.4" 2022-07-19 LTS OpenJDK Runtime Environment Zulu17.36+13-CA (build 17.0.4+8-LTS) OpenJDK 64-Bit Server VM Zulu17.36+13-CA (build 17.0.4+8-LTS, mixed mode, sharing) {code} I reported this issue for the record just in case it already happened in the past. Now you know you have a way to reproduce it ;-) ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)