Sanity tests failing in fortinet.fortimanager

[dmsimard]

Greetings from the Ansible community working group,

The fortinet.fortimanager collection is included in the Ansible community package (ansible on PyPI) and as such is expected to have CI which runs and passes sanity tests (amongst other things) as per documented here: https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst#ci-testing

When running ansible-test sanity --docker on the latest version of the collection (2.1.5), we found that it took over fourty (40) hours to complete (recorded here), largely due to pylint getting stuck or struggling to go through the collection. In comparison, running sanity tests on 2.1.4 completed in ~7m15s.

We have not been able to find why pylint takes so long in 2.1.5 and leave it up to the maintainers to troubleshoot.

For the time being, we are considering temporarily reverting the version included in ansible back to 2.1.4.

If the collection is not improved to meet the collection inclusion specifications in the near future, it may also be at risk of being removed from the community package.

Please acknowledge the issue and keep us updated. Thank you.

[gundalow]

Although not ideal, running ansible-test sanity with --skip-test pylint would be an improvement over what we have today.

[dmsimard]

Linking this issue to the community topic on sanity tests: ansible-community/community-topics#96

The list of sanity test errors for this collection is available here: https://gist.githubusercontent.com/dmsimard/14e04158302003216a0bd7edfe2db110/raw/5774e739395c20fdffd63b98f33540eae043ded3/output.txt

[dmsimard]

@JieX19 would it be possible to address the sanity test failures soon ?