tkobayas opened a new issue, #3320:
URL: https://github.com/apache/incubator-kie-kogito-runtimes/issues/3320

   ### Describe the bug
   
   
org.kie.kogito.quarkus.workflows.CallbackStateTimeoutsIT.callbackStateTimeoutsExceeded
   
org.kie.kogito.quarkus.workflows.CallbackStateWithTimeoutsErrorHandlerIT.callbackStateTimeoutsExceeded
   org.kie.kogito.quarkus.workflows.EventTimedoutIT.testTimedout
   
   These tests are flaky. Even if I set a longer timeout value (e.g. from 10 
sec to 60 sec), the tests may still fail.
   
   Until they get stable, it's better to `@Disable` the tests.
   
   ### Expected behavior
   
   These tests pass stably.
   
   Until then, disabled the tests.
   
   ### Actual behavior
   
   These tests fail occasionally in both CIs and local. (Around 30% chance of 
failing)
   
   ```
   2023-12-06 12:17:27,667 INFO  
[org.kie.kog.ser.wor.dev.DevModeServerlessWorkflowLogger] (executor-thread-1) 
Triggered node 'TimerNode_14' for process 'callback_state_timeouts' 
(afb4bfef-8418-49d5-ac62-de009d062af8)
   2023-12-06 12:17:27,668 INFO  
[org.kie.kog.ser.wor.dev.DevModeServerlessWorkflowLogger] (executor-thread-1) 
Triggered node 'callbackEvent' for process 'callback_state_timeouts' 
(afb4bfef-8418-49d5-ac62-de009d062af8)
   2023-12-06 12:17:27,669 INFO  
[org.kie.kog.ser.wor.dev.DevModeServerlessWorkflowLogger] (executor-thread-1) 
Workflow 'callback_state_timeouts' (afb4bfef-8418-49d5-ac62-de009d062af8) was 
started, now 'Active'
   2023-12-06 12:17:32,667 INFO  [org.kie.kog.ser.job.imp.InMemoryJobService] 
(executor-thread-1) Job af217e82-9d62-48ae-a906-aa6dfa07b82c started
   [ERROR] Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
34.03 s <<< FAILURE! -- in 
org.kie.kogito.quarkus.workflows.CallbackStateTimeoutsIT
   [ERROR] 
org.kie.kogito.quarkus.workflows.CallbackStateTimeoutsIT.callbackStateTimeoutsExceeded
 -- Time elapsed: 10.43 s <<< ERROR!
   org.testcontainers.shaded.org.awaitility.core.ConditionTimeoutException: 
   Assertion condition defined as a 
org.kie.kogito.test.utils.ProcessInstancesRESTTestUtils 1 expectation failed.
   Expected status code <404> but was <200>.
    within 10 seconds.
        at 
org.testcontainers.shaded.org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
        at 
org.testcontainers.shaded.org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
        at 
org.testcontainers.shaded.org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
        at 
org.testcontainers.shaded.org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
        at 
org.testcontainers.shaded.org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:769)
        at 
org.kie.kogito.test.utils.ProcessInstancesRESTTestUtils.assertProcessInstanceHasFinished(ProcessInstancesRESTTestUtils.java:161)
        at 
org.kie.kogito.quarkus.workflows.CallbackStateTimeoutsIT.callbackStateTimeoutsExceeded(CallbackStateTimeoutsIT.java:61)
   ```
   
   ### How to Reproduce?
   
   Run these tests under 
`kogito-runtimes/quarkus/extensions/kogito-quarkus-serverless-workflow-extension/kogito-quarkus-serverless-workflow-integration-test`
   
   $ mvn verify
   
   ### Output of `uname -a` or `ver`
   
   Linux tkobayas.nrt.csb 4.18.0-477.27.1.el8_8.x86_64 #1 SMP Thu Aug 31 
10:29:22 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux
   
   ### Output of `java -version`
   
   openjdk version "17.0.9" 2023-10-17 LTS
   
   ### GraalVM version (if different from Java)
   
   _No response_
   
   ### Kogito version or git rev (or at least Quarkus version if you are using 
Kogito via Quarkus platform BOM)
   
   `quarkus-3.2LTS` branch
   
   ### Build tool (ie. output of `mvnw --version` or `gradlew --version`)
   
   Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
   
   ### Additional information
   
   _No response_


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