Split AWS jobs even more #962
Conversation
|
@goneri Can you confirm there's no other way I can do this? On community.aws right now with 5 splits I have 3 jobs that take <23 minutes but 1 that takes more than an hour - so I have to try 6 splits. We're going to be at risk of hitting API call thresholds at this rate. I know which test suites shouldn't be in the same group but I don't know any way to manually assign tests to groups in zuul like we could with shippable. Is there something I could be doing to have more control over this? |
We can certainly improve this. The split is done here: https://github.com/ansible/ansible-zuul-jobs/blob/master/roles/ansible-test/tasks/split_targets.yaml#L2 Can we split up this longer test targets? e.g split up |
|
Every time we increase the number of // job we also increase the CI resource consumption. We also get closer to the situation where we can hit API rate limit problems. At this stage, I would prefer we put this PR on hold and wait a bit to see how #969 improve the situation. We can also split up these slow targets. |
Migrates scenario guide from ansible/ansible repo SUMMARY Related to ansible-community/antsibull-build#255. Do we need to rename the page index.rst? Or add an index.rst file? Also needs a PR against ansible/ansible removing this content from there. ISSUE TYPE Docs Pull Request COMPONENT NAME docs.ansible.com Depends-On: ansible/ansible-zuul-jobs#962 Reviewed-by: Mark Chappell <None> Reviewed-by: Alicia Cozine <None> Reviewed-by: Jill R <None>
Group 2 is timing out a lot