-
Notifications
You must be signed in to change notification settings - Fork 30
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
Sanity tests failing in chocolatey.chocolatey #78
Comments
Thanks for letting us know! I'll re-verify these results against the current master branch and see what's still outstanding, and then we'll look to get a release sorted out. Most if not all of the PowerShell ones may already be fixed at the latest commit, and any that remain I'll file PRs to sort out; they should be straightforward. The ones I'm less sure of are the module documentation errors. Is there a doc page listing examples of how these external module / option references are supposed to be listed? I can take a stab at it, but I'd rather have a good idea of what I'm doing first there. 🙂 |
Hey and thanks for looking into this.
@vexx32 For what it's worth, I've reran the tests against the same release but by installing with Some of these might be new from ansible-core or ansible-test 2.13, the changelog is here: https://github.com/ansible/ansible/blob/stable-2.13/changelogs/CHANGELOG-v2.13.rst
I haven't investigated yet but I know there's at least the following docs:
@pauby there's a broad scope in the linked issue that may take longer but in the meantime it'd be great if we could get the number of sanity tests errors (across every included collections) down in time for the release of ansible 6.0.0, 2022-06-21 (see roadmap). In other words, it's not the end of the world but we would be grateful if you had the opportunity to fix the errors or put them in an ignore file (like this example, if appropriate) and tag a new release by feature freeze on 2022-05-24. |
I have rerun the test against the latest collection build from Github and noted/confirmed the following issues:
|
Rename some functions to use singular nouns per linting guidelines.
Added a process block for `ConvertFrom-Stdout` which was missing it.
Normalised the amount of whitespace used for hashtable declarations and a few other cases. Added suppression attributes around module specs due to their propensity to become rather complicated, where the extra whitespace is generally helpful for readability. Also added suppression to the simpler module specs for consistency.
Split up some error messages into separate lines to avoid this lint; hopefully it makes them a bit easier to read in code as well.
Linter in newer ansible versions (rightly) makes a fuss about possibly unclear module names, so I've added the correct module prefixes to all M() module references, and also to some `seealso` sections that according to docs are supposed to use FQCN as well.
Earlier attempt didn't seem to manage the suppression properly.
Normalised the amount of whitespace used for hashtable declarations and a few other cases. Added suppression attributes around module specs due to their propensity to become rather complicated, where the extra whitespace is generally helpful for readability. Also added suppression to the simpler module specs for consistency.
Split up some error messages into separate lines to avoid this lint; hopefully it makes them a bit easier to read in code as well.
Linter in newer ansible versions (rightly) makes a fuss about possibly unclear module names, so I've added the correct module prefixes to all M() module references, and also to some `seealso` sections that according to docs are supposed to use FQCN as well.
SUMMARY
We are running sanity tests across every collection included in the Ansible community package (as part of this issue) and found that
ansible-test sanity --docker
against chocolatey.chocolatey 1.2.0 fails with ansible-core 2.13.0rc1 in ansible 6.0.0a2.ISSUE TYPE
COMPONENT NAME
n/a
ANSIBLE VERSION
COLLECTION VERSION
STEPS TO REPRODUCE
ansible-test sanity --docker
EXPECTED RESULTS
Tests are either passing or ignored.
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: