Closed rvalle closed 4 years ago
@rvalle the common reason for such problems is that ignore-2.9.txt is out of date since 2.9's ansible-test isn't used for sanity tests. @resmo are you running tests only with ansible-test from devel, or also from stable-2.10 and/or stable-2.9? (Since ignore-2.10.txt looks very similarly to ignore-2.9.txt, I guess it also hasn't been updated. Since ignore-2.11.txt isn't there I guess all actual problems have been resolved.)
I am using ansible-base instead of ansible 2.9. Sanity and Unit tests have some failures I guess related to the migration deadline #14 Integration tests seem to work as expected, with only some (ignored) failures, which I assume are WIP or similar.
this is fixed by #19
Hi,
I am trying to setup my dev environment before contributing here. One question outstanding is how to test these modules now that they are not part of ansible. There is a relevant discussion here: https://github.com/ansible/ansible/issues/60215
But I got tests to start working by setting my repo in a special directory, cloning at:
It seems to be required to move/rename the repository so the hierarchy from ansible_collections... is there. I also create a virtual environent at /src/venv and install ansible (2.9) and cs.
And then tests will start running with:
both unit/sanity tests are reporting a number of issues, and I wonder whether this is development environment issue or the code needs fixing.
For example:
when running unit tests:
Or when running sanity tests:
I find it hard to believe that there are so many outstanding issues as Ansible's release process is very demanding and this collection was release as part as ansible:
I wonder if: