Skip to content
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

Jump to bottom

Possible problems in CamelSinkAWSSQSITCase tests #215

Closed
valdar opened this issue May 16, 2020 · 2 comments
Closed

Possible problems in CamelSinkAWSSQSITCase tests #215

valdar opened this issue May 16, 2020 · 2 comments
Labels
bug Something isn't working flaky test Involving tests that expose a flaky behaviour

Comments

@valdar
Copy link
Member

valdar commented May 16, 2020

While refactoring tests to accommodate syslog test I properly implemented the initializeConnectorBlocking function and started to have random failures from CamelSinkAWSSQSITCase. For the moment I changed it to use initializeConnector.

Logically there should be no differences in the test outcome using one method or the other, but in case of initializeConnectorBlocking there is.
@valdar valdar added bug Something isn't working flaky test Involving tests that expose a flaky behaviour labels May 16, 2020
@valdar
Copy link
Member Author

valdar commented May 16, 2020

cc: @orpiske

@orpiske
Copy link
Contributor

orpiske commented May 16, 2020

@valdar thanks, I'll look into this one.

orpiske added a commit to orpiske/camel-kafka-connector that referenced this issue May 20, 2020
@orpiske
Updated to use blocking as part of investigation of issue apache#215
5aefea1
orpiske added a commit to orpiske/camel-kafka-connector that referenced this issue May 20, 2020
@orpiske
Updated to use blocking as part of investigation of issue apache#215
3eb95cf
@orpiske orpiske mentioned this issue May 20, 2020
Merged
orpiske added a commit to orpiske/camel-kafka-connector that referenced this issue May 20, 2020
@orpiske
Updated to use blocking as part of investigation of issue apache#215
c13892b
orpiske added a commit to orpiske/camel-kafka-connector that referenced this issue May 21, 2020
@orpiske
Updated to use blocking as part of investigation of issue apache#215
df0d7f6
orpiske added a commit to orpiske/camel-kafka-connector that referenced this issue May 25, 2020
@orpiske
Updated to use blocking as part of investigation of issue apache#215
98ac066
orpiske added a commit to orpiske/camel-kafka-connector that referenced this issue May 25, 2020
@orpiske
Create the Queue before the test to avoid erractic test behavior
b15f64f 
Also updates the CamelSinkAWSSQSITCase to use the blocking connector
runtime initialization.

This solves issue apache#215
orpiske added a commit to orpiske/camel-kafka-connector that referenced this issue May 25, 2020
@orpiske
Create the Queue before the test to avoid erractic test behavior
5662b77 
Also updates the CamelSinkAWSSQSITCase to use the blocking connector
runtime initialization.

This solves issue apache#215

Repeat the test a few more times to ensure it is stable
@orpiske orpiske mentioned this issue May 25, 2020
Merged
@valdar valdar closed this as completed Jun 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working flaky test Involving tests that expose a flaky behaviour
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@valdar @orpiske