-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IndexOutOfBoundsException while running test #71
Comments
@berndruecker Could you possibly share the test code with us? |
Sure thing - here it is: https://github.com/berndruecker/camunda-cloud-zeebe-tests-playgorund/blob/main/src/test/java/io/berndruecker/playground/zeebe/tests/SimpleJavaTest.java (Ignore the other Spring Stuff - I also try to get a test running in the Spring Boot environment in parallel to validate a realistic test scenario). PS: I am collecting feedback separately and might propose a quick call to go through this separately... |
Just talked to Holisticon today and they reported that they see this problem massively - the faster the machine the more often they saw it. Seems like there is some threading/race condition |
@Zelldon / @saig0 Might also be interesting for you. Could it be that we are writing to the buffer and reading from it at the same time? |
Thanks for mentioning me. I run into the same issue when I created new tests for the chaos workers and used eze camunda/zeebe-chaos@8c8c774 I fixed it in eze, see here camunda-community-hub/eze@949804a |
It might not appear in your code anymore since you changed the implementation. |
Thanks for sharing @Zelldon 🙇 Since we removed the use of exporters we will not run into this issue anymore. Therefore I will close this issue. |
I had it occur again. I tried to reactive the idle state monitor. It fails if there is an underlying exception as mentioned above |
I think the issue is in your https://github.com/camunda-cloud/camunda-cloud-testing/blob/4a9346b2456b8cc44ec9ea87fc7c6f23b1cc12df/src/main/java/io/camunda/zeebe/bpmnassert/testengine/IdleStateMonitor.java#L11 where the processor (#onProcessed) can cause changes to the reader and the logstorage (#onCommit). |
I just tried the current snapshot and run a test. During one test run, I saw this exception - seemed to be a race condition - as I could not reproduce it.
I just wanted to flag it here - feel free to close given the current state of the testing library
The text was updated successfully, but these errors were encountered: