-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust booleans from yes/no to true/false #978
Adjust booleans from yes/no to true/false #978
Conversation
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
recheck |
recheck |
Hi @alinabuzachis, for the record #979 addresses the timeout problem. |
recheck |
recheck |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
regate |
regate |
@goneri One of the ec2_instance tests is constantly failing here. |
Hi @alinabuzachis, The problem comes from As far as I understand, amazon.aws/plugins/modules/ec2_vol.py Lines 554 to 555 in d73b395
I'm not sure if it's some sporadic API inconsistency or a recent change somewhere. |
regate |
Regarding the TIMED_OUT errors, it looks the tests are slower than usual. We can try to run less targets in the same jobs if the problem occures too often. |
This looks like a similar problem. 2022-09-13 16:49:22.761417 | controller | "state": { And so when the |
regate |
tests: some ec2_instance targets are slower than normal Depends-On: ansible/ansible-zuul-jobs#1625 Dedicate more time for the execution of some slow ec2_instance targets. See: #978 (comment)
recheck |
recheck |
Signed-off-by: Alina Buzachis <[email protected]>
d6f8de4
to
b788096
Compare
Backport to stable-3: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply b4298bd on top of patchback/backports/stable-3/b4298bddef81caf7739e951defb62af0fbd12d5a/pr-978 Backporting merged PR #978 into main
🤖 @patchback |
Backport to stable-4: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply b4298bd on top of patchback/backports/stable-4/b4298bddef81caf7739e951defb62af0fbd12d5a/pr-978 Backporting merged PR #978 into main
🤖 @patchback |
SUMMARY
As per ansible-community/community-topics#116
See also ansible-collections/community.aws#1420
Closes: #1041
ISSUE TYPE
COMPONENT NAME
several
ADDITIONAL INFORMATION