Skip to content

Conversation

dmsimard
Copy link
Contributor

  • The number of tests is growing and it's getting a bit unyieldy.
    Break them up a bit so we can add more tests easily.

  • Add an "antsibull_run_sanity" argument to loop over the collections in
    the release tarball to run "ansible-test sanity --docker" on them.

@dmsimard
Copy link
Contributor Author

The sanity tests timed out after 6h, it looks like there's something wrong with fortinet.fortimanager on which ansible-test gets stuck endlessly. Will troubleshoot later.

@felixfontein
Copy link
Collaborator

That collection has a 33 MB module directory, with at least one module > 1 MB. I'm not surprised that this happens.

I don't think this should be part of the release role. It should be separate, and it should not be part of this repo, but in ansible-build-data.

- The number of tests is growing and it's getting a bit unyieldy.
  Break them up a bit so we can add more tests easily.

- Add an "antsibull_run_sanity" argument to loop over the collections in
  the release tarball to run "ansible-test sanity --docker" on them.
@dmsimard
Copy link
Contributor Author

Going to close this in favor of ansible-community/ansible-build-data#122.

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