resolve 100+ ansible-test sanity issues. #498
Comments
toumorokoshi
added a commit
to toumorokoshi/google.cloud
that referenced
this issue
Sep 23, 2022
As a first step to rehabilitate the google.cloud repository, adding actions to help ensure that the collection is still passing tests as changes are merged. Details: - ansible-devel was not added to the matrix since it may destablize the tests, primarily used to validate the collection. - running sanity tests reported over 100+ issues, backlogged to ansible-collections#498 before turning those on.
toumorokoshi
added a commit
to toumorokoshi/google.cloud
that referenced
this issue
Sep 23, 2022
As a first step to rehabilitate the google.cloud repository, adding actions to help ensure that the collection is still passing tests as changes are merged. Details: - ansible-devel was not added to the matrix since it may destablize the tests, primarily used to validate the collection. - running sanity tests reported over 100+ issues, backlogged to ansible-collections#498 before turning those on.
toumorokoshi
added a commit
that referenced
this issue
Sep 23, 2022
As a first step to rehabilitate the google.cloud repository, adding actions to help ensure that the collection is still passing tests as changes are merged. Details: - ansible-devel was not added to the matrix since it may destablize the tests, primarily used to validate the collection. - running sanity tests reported over 100+ issues, backlogged to #498 before turning those on.
|
closing as duplicate of #482 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
It seems that
ansible-test sanitycatches over 100+ issues with the collection today: https://github.com/ansible-collections/google.cloud/actions/runs/3114655550/jobs/5050740740.Before sanity tests can be turned on, those will have to be resolved.
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
2.13
COLLECTION VERSION
head
The text was updated successfully, but these errors were encountered: