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

[Backport 2024.2] Use streaming instead of RBNO for a few longevity tests #8648

Merged
merged 2 commits into from
Sep 11, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Sep 11, 2024

Overview

  • Use streaming for one tier1 (longevity-mv-si-4days) and one tier2 (longevity-cdc-8h-multi-dc-topology-changes) longevity tests

Testing

  • Run longevity-mv-si-4days in jenkins
  • Run longevity-cdc-8h-multi-dc-topology-changes in jenkins

PR pre-checks (self review)

  • I added the relevant backport labels
  • I didn't leave commented-out/debugging code

Questions

  • Are those two tests enough? Should I add more tests from different categories?
    • Are those even right tests?
  • How can I verify that it uses streaming?
  • For how long do I need to run tests to verify correctness of this PR?

Fixes #8289

(cherry picked from commit 3f30982)

(cherry picked from commit d722f0d)

Parent PR: #8402

…nges.jenkinsfile

Rename to longevity-cdc-8h-multi-dc-topology-changes-streaming.jenkinsfile
Move old version to longevity/longevity-cdc-8h-multi-dc-topology-changes.jenkinsfile

-

(cherry picked from commit 3f30982)
Rename to longevity-mv-si-4days-streaming.jenkinsfile
Move old version to longevity/longevity-mv-si-4days.jenkinsfile

(cherry picked from commit d722f0d)
@mergify mergify bot assigned pehala Sep 11, 2024
@fruch fruch merged commit 46b2a15 into branch-2024.2 Sep 11, 2024
7 checks passed
@mergify mergify bot deleted the mergify/bp/branch-2024.2/pr-8402 branch September 11, 2024 20:35
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.

2 participants