[ 
https://issues.apache.org/jira/browse/CAMEL-23907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aurélien Pupier reopened CAMEL-23907:
-------------------------------------

still failing with same frequency 
https://develocity.apache.org/scans/tests?search.relativeStartTime=P90D&search.rootProjectNames=camel&search.timeZoneId=Europe%2FParis&tests.container=org.apache.camel.processor.ThreadsRejectedExecutionTest

{noformat}
[camel-core] [ERROR] Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time 
elapsed: 7.547 s <<< FAILURE! -- in 
org.apache.camel.processor.ThreadsRejectedExecutionTest
[camel-core] [ERROR] 
org.apache.camel.processor.ThreadsRejectedExecutionTest.testThreadsRejectedAbortNoRedelivery
 -- Time elapsed: 4.104 s <<< FAILURE!
org.opentest4j.AssertionFailedError: Expected 0 messages at mock:error but got 
1 ==> expected: <0> but was: <1>
        at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:601)
        at 
org.apache.camel.processor.ThreadsRejectedExecutionTest.testThreadsRejectedAbortNoRedelivery(ThreadsRejectedExecutionTest.java:197)
{noformat}

> Flaky test: ThreadsRejectedExecutionTest in camel-core
> ------------------------------------------------------
>
>                 Key: CAMEL-23907
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23907
>             Project: Camel
>          Issue Type: Test
>          Components: camel-core
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>            Priority: Major
>              Labels: flaky-test
>             Fix For: 4.22.0
>
>
> The test `ThreadsRejectedExecutionTest.testThreadsRejectedAbortNoRedelivery` 
> in `camel-core` is flaky in CI.
> Observed failure on JDK 25 in PR #24358 CI run (July 4, 2025). This test 
> involves thread pool rejection with abort policy, which is timing-sensitive.
> The test should be stabilized, potentially using Awaitility instead of any 
> timing-dependent assertions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to