Shekharrajak opened a new issue, #19463:
URL: https://github.com/apache/druid/issues/19463

   IngestionSmokeTest hits the 20 s LatchableEmitter timeout intermittently on 
the JDK 25 CI matrix (test-jdk25-[I*,A*,U*]). Three unrelated methods fail in 
the same run, all at the exact 20 s wall — a load/timing pattern, not a 
regression.
   
   
   ```
     
embedded-tests/target/test-classes/org/apache/druid/testing/embedded/indexing/IngestionSmokeTest.class:282
 | Timed out waiting for event after [20,000]ms 20.391s
     
embedded-tests/target/test-classes/org/apache/druid/testing/embedded/indexing/IngestionSmokeTest.class:337
 | Timed out waiting for event after [20,000]ms 20.015s
     
embedded-tests/target/test-classes/org/apache/druid/testing/embedded/indexing/IngestionSmokeTest.class:166
 | Timed out waiting for event after [20,000]ms 20.019s
     ℹ️ Posting with conclusion 'failure' to 
https://github.com/apache/druid/pull/19311 (sha: 
2d094d5fbe6e11b6d22b1df8bf54c8cf7b7d03d2)
   🚀 Publish results
     ℹ️ - Test Report - test-jdk25-[I*,A*,U*] - 18604 tests run, 17847 passed, 
754 skipped, 3 failed.
        🧪 - 
embedded-tests/target/test-classes/org/apache/druid/testing/embedded/indexing/IngestionSmokeTest.class
 | Timed out waiting for event after [20,000]ms
        🧪 - 
embedded-tests/target/test-classes/org/apache/druid/testing/embedded/indexing/IngestionSmokeTest.class
 | Timed out waiting for event after [20,000]ms
        🧪 - 
embedded-tests/target/test-classes/org/apache/druid/testing/embedded/indexing/IngestionSmokeTest.class
 | Timed out waiting for event after [20,000]ms
   
   ```


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to