-
Notifications
You must be signed in to change notification settings - Fork 115
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
Skip orphan cleanup case for n_minus scenario #14371
Skip orphan cleanup case for n_minus scenario #14371
Conversation
@vsedmik @damoore044 Lets wait for cherrypicks of NMinus to merge else the cherrypicks here will fail. Or since its blocking the test in master from running we can merge this and manually cherrypick them later. I really wish we will bring back the Autocherrypick of Merged PRs! |
Let me update the codebase to include that again ? @jyejare |
@omkarkhatavkar lets discuss that in tomorrows call. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ack, locally this case works as expected now!
(cherry picked from commit 672ba8d)
(cherry picked from commit 672ba8d)
(cherry picked from commit 672ba8d)
Skip orphan cleanup case for n_minus scenario (#14371) (cherry picked from commit 672ba8d) Co-authored-by: vsedmik <[email protected]>
Skip orphan cleanup case for n_minus scenario (#14371) (cherry picked from commit 672ba8d) Co-authored-by: vsedmik <[email protected]>
Skip orphan cleanup case for n_minus scenario (#14371) (cherry picked from commit 672ba8d) Co-authored-by: vsedmik <[email protected]>
…4409) Skip orphan cleanup case for n_minus scenario (SatelliteQE#14371) (cherry picked from commit 672ba8d) Co-authored-by: vsedmik <[email protected]>
Problem Statement
Orphan cleanup test case should be skipped for n_minus scenario but run in normal runs.
Solution
Flip the logic.