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

Allow to specify which sanity tests to run / skip / enable #73

Merged
merged 2 commits into from
Apr 3, 2024

Conversation

felixfontein
Copy link
Contributor

Includes a refactor to generate all ansible-test parameters with Python code.

Skipping specific sanity tests is needed when these totally break due to bugs, see for example ansible/ansible#82574. There is no way to ignore the failure fixed by that PR with ignore.txt.

@felixfontein felixfontein force-pushed the skip branch 2 times, most recently from 4c8a42e to a4a6bce Compare January 21, 2024 12:07
action.yml Outdated Show resolved Hide resolved
action.yml Show resolved Hide resolved
@webknjaz
Copy link
Member

@felixfontein sorry, I only now noticed this PR. Could you separate refactoring/restructuring, linter adjustments and actual functional changes so they could be accepted/reviewed separately?

@felixfontein
Copy link
Contributor Author

@webknjaz I moved the refactoring to #75.

@felixfontein felixfontein force-pushed the skip branch 2 times, most recently from 973da73 to 0f8ef12 Compare March 30, 2024 22:09
This is useful when tests totally fail (skipping tests), or when
sanity tests take too long and should be split up into parallel jobs
(skipping and explicitly picking tests), or to enable tests that
are disabled by default (like deprecation by date expiry).
@webknjaz
Copy link
Member

FTR I clicked the "rebase" button on GH UI.

action.yml Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <sviat@redhat.com>
@webknjaz
Copy link
Member

webknjaz commented Apr 2, 2024

@felixfontein are you making any more changes here or should I consider merging?

@webknjaz
Copy link
Member

webknjaz commented Apr 3, 2024

Going to merge this using the squash strategy. Scratch that. We already have merge queues here. No squash for you :)

@webknjaz webknjaz added this pull request to the merge queue Apr 3, 2024
Merged via the queue into ansible-community:main with commit 950f0eb Apr 3, 2024
9 checks passed
@felixfontein felixfontein deleted the skip branch April 7, 2024 13:44
@felixfontein
Copy link
Contributor Author

@webknjaz yes, sorry, I was done here :) Thanks for reviewing and merging!

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