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.

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

KAFKA-10308 fix flaky core/round_trip_fault_test.py #9079

Merged
merged 2 commits into from
Aug 4, 2020

Conversation

chia7712
Copy link
Contributor

@chia7712 chia7712 commented Jul 25, 2020

Creating a topic may fail (due to timeout) in running system tests. However, RoundTripWorker does not ignore TopicExistsException which makes round_trip_fault_test.py be a flaky one.

More specifically, a network exception can cause the CreateTopics request to reach Kafka but Trogdor retry it
and hit a TopicAlreadyExists exception on the retry, failing the test.

Committer Checklist (excluded from commit message)

  • Verify design and implementation
  • Verify test coverage and CI build status
  • Verify documentation (including upgrade notes)

@ijuma
Copy link
Contributor

ijuma commented Jul 25, 2020

retest this please

@chia7712
Copy link
Contributor Author

org.apache.kafka.streams.integration.EosBetaUpgradeIntegrationTest > shouldUpgradeFromEosAlphaToEosBeta[true] FAILED

the failed test is unrelated to this PR. retest this please

@chia7712
Copy link
Contributor Author

@ijuma Could you please take a look?

@ijuma
Copy link
Contributor

ijuma commented Aug 4, 2020

ok to test

Copy link
Contributor

@ijuma ijuma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ijuma ijuma merged commit dccc82e into apache:trunk Aug 4, 2020
ijuma pushed a commit that referenced this pull request Aug 4, 2020
Creating a topic may fail (due to timeout) in running system tests. However, `RoundTripWorker` does not ignore `TopicExistsException` which makes `round_trip_fault_test.py` be a flaky one.

More specifically, a network exception can cause the `CreateTopics` request to reach Kafka but Trogdor retry it
and hit a `TopicAlreadyExists` exception on the retry, failing the test.

Reviewers: Ismael Juma <ismael@juma.me.uk>
@stanislavkozlovski
Copy link
Contributor

@ijuma considering this is causing the system test to be flaky, is it worth backporting? It seems like the test is present since 1.1

ijuma pushed a commit that referenced this pull request Aug 20, 2020
Creating a topic may fail (due to timeout) in running system tests. However, `RoundTripWorker` does not ignore `TopicExistsException` which makes `round_trip_fault_test.py` be a flaky one.

More specifically, a network exception can cause the `CreateTopics` request to reach Kafka but Trogdor retry it
and hit a `TopicAlreadyExists` exception on the retry, failing the test.

Reviewers: Ismael Juma <ismael@juma.me.uk>
ijuma pushed a commit that referenced this pull request Aug 20, 2020
Creating a topic may fail (due to timeout) in running system tests. However, `RoundTripWorker` does not ignore `TopicExistsException` which makes `round_trip_fault_test.py` be a flaky one.

More specifically, a network exception can cause the `CreateTopics` request to reach Kafka but Trogdor retry it
and hit a `TopicAlreadyExists` exception on the retry, failing the test.

Reviewers: Ismael Juma <ismael@juma.me.uk>
ijuma pushed a commit that referenced this pull request Aug 20, 2020
Creating a topic may fail (due to timeout) in running system tests. However, `RoundTripWorker` does not ignore `TopicExistsException` which makes `round_trip_fault_test.py` be a flaky one.

More specifically, a network exception can cause the `CreateTopics` request to reach Kafka but Trogdor retry it
and hit a `TopicAlreadyExists` exception on the retry, failing the test.

Reviewers: Ismael Juma <ismael@juma.me.uk>
@chia7712 chia7712 deleted the KAFKA-10308 branch March 25, 2024 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants