Skip to content

fix: flaxy EventProcessorTest.triggerOnAllEventDeleteEventInstantlyAfterEvent #3003

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 17, 2025
+3 −1
Merged

fix: flaxy EventProcessorTest.triggerOnAllEventDeleteEventInstantlyAfterEvent #3003

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d02c093
fix: flaxy EventProcessorTest.triggerOnAllEventDeleteEventInstantlyAf…
csviri Oct 16, 2025
a4e9ef0
fix: typo
metacosm Oct 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ...k-core/src/test/java/io/javaoperatorsdk/operator/processing/event/EventProcessorTest.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -562,7 +562,9 @@ void triggerOnAllEventDeleteEventInstantlyAfterEvent() {
eventProcessor.handleEvent(prepareCRDeleteEvent1());

waitUntilProcessingFinished(eventProcessor, TestUtils.testCustomResource1Id());
verify(reconciliationDispatcherMock, times(1)).handleExecution(any());
// it is expected to be usually called only once, but it can happen based on timing that called
// twice
verify(reconciliationDispatcherMock, atMost(2)).handleExecution(any());
}

@Test
Expand Down