-
Notifications
You must be signed in to change notification settings - Fork 541
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
[tests] all cleaner tests to have --no-update option #3254
Comments
I'd be ok with this, if we add a test that does not include |
Such a test makes sense; maybe worth backing the mapping file prior such test and restoring the original afterwards, just to be sure. |
dtzhou2
pushed a commit
to dtzhou2/sos
that referenced
this issue
Jun 22, 2023
Added default mapping test and made it so all cleaner tests have the --no-update option as in issue sosreport#3254
1 task
dtzhou2
pushed a commit
to dtzhou2/sos
that referenced
this issue
Jun 26, 2023
Added default mapping test and made it so all cleaner tests have the --no-update option as in issue sosreport#3254
dtzhou2
pushed a commit
to dtzhou2/sos
that referenced
this issue
Jul 3, 2023
Added default mapping test and made it so all cleaner tests have the --no-update option as in issue sosreport#3254 Signed-off-by: Daniel Zhou <dzhou@redhat.com>
dtzhou2
pushed a commit
to dtzhou2/sos
that referenced
this issue
Jul 3, 2023
[avocado_tests] added default_mapping test Added default mapping test and made it so all cleaner tests have the --no-update option as in issue sosreport#3254 Signed-off-by: Daniel Zhou <dzhou@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running independent tests one after another, some
sos cleaner
can update/etc/sos/cleaner/default_mapping
by unexpected value which can break further avocado tests.Any
sos clean
test in avocado must have--no-update
option to prevent thedefault_mapping
update.The text was updated successfully, but these errors were encountered: