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

qa: correct line processing logic #1762

Merged
merged 1 commit into from Jun 6, 2022
Merged

qa: correct line processing logic #1762

merged 1 commit into from Jun 6, 2022

Conversation

batrick
Copy link
Member

@batrick batrick commented Jun 6, 2022

Most runs don't use --no-nested-subset and for those that used --subset,
the if conditions would correctly pickup "seed" (when it mattered).
However, when --subset was not specified in the original run, the "seed"
was not correctly picked up. Therefore, the result of inserting the "if
no_nested_subset is None:" before the "elif seed is None:" caused it to
never read the seed for most folks teuthology runs.

Signed-off-by: Patrick Donnelly pdonnell@redhat.com

Most runs don't use --no-nested-subset and for those that used --subset,
the if conditions would correctly pickup "seed" (when it mattered).
However, when --subset was not specified in the original run, the "seed"
was not correctly picked up. Therefore, the result of inserting the "if
no_nested_subset is None:" before the "elif seed is None:" caused it to
never read the seed for most folks teuthology runs.

Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
@neha-ojha neha-ojha requested a review from zmc June 6, 2022 18:27
batrick added a commit to batrick/teuthology that referenced this pull request Jun 6, 2022
Most runs don't use --no-nested-subset and for those that used --subset,
the if conditions would correctly pickup "seed" (when it mattered).
However, when --subset was not specified in the original run, the "seed"
was not correctly picked up. Therefore, the result of inserting the "if
no_nested_subset is None:" before the "elif seed is None:" caused it to
never read the seed for most folks teuthology runs.

Fixes: ceph#1762
Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
@batrick batrick closed this Jun 6, 2022
@batrick batrick deleted the nested-subset-fix branch June 6, 2022 18:55
@batrick batrick restored the nested-subset-fix branch June 6, 2022 18:55
@batrick
Copy link
Member Author

batrick commented Jun 6, 2022

Accidentally closed this

@batrick batrick reopened this Jun 6, 2022
@batrick
Copy link
Member Author

batrick commented Jun 6, 2022

nevermind, found the reopen button!

Copy link
Member

@zmc zmc left a comment

Choose a reason for hiding this comment

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

This is a good fix but it doesn't change issue 55815, which is reproducible when passing --seed

@zmc zmc merged commit 93d2b65 into main Jun 6, 2022
@zmc zmc deleted the nested-subset-fix branch June 6, 2022 21:17
@zmc
Copy link
Member

zmc commented Jun 7, 2022

I was wrong - this fixes the main use-case! There appears to be a separate issue affecting some runs that cause incorrect behavior when the archive is unavailable, even when passing correct values, but I'm very glad to have this fixed. Thanks!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants