1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00

disable windows loop async test

Fails pretty regularly on Shippable/AWS, never locally- always seems to be on the last async task in the loop.
This commit is contained in:
nitzmahone 2016-09-06 22:13:31 -07:00
parent c752b25ced
commit 7a9395b5e0

View file

@ -138,31 +138,33 @@
- asyncresult | failed == true - asyncresult | failed == true
- asyncresult.msg is search('failing via exception') - asyncresult.msg is search('failing via exception')
- name: loop async success
async_test:
sleep_delay_sec: 3
async: 10
poll: 0
with_sequence: start=1 end=4
register: async_many
- name: wait for completion # this test is only flaky under shippable/AWS- the last iteration "until's" forever, cannot repro locally
async_status: #- name: loop async success
jid: "{{ item }}" # async_test:
register: asyncout # sleep_delay_sec: 3
until: asyncout.finished == 1 # async: 10
retries: 10 # poll: 0
delay: 1 # with_sequence: start=1 end=4
with_items: "{{ async_many.results | map(attribute='ansible_job_id') | list }}" # register: async_many
#
- name: validate results #- name: wait for completion
assert: # async_status:
that: # jid: "{{ item }}"
- item.finished == 1 # register: asyncout
- item.slept_sec == 3 # until: asyncout.finished == 1
- item.changed == true # retries: 10
- item.ansible_job_id is match('\d+\.\d+') # delay: 1
with_items: "{{ asyncout.results }}" # with_items: "{{ async_many.results | map(attribute='ansible_job_id') | list }}"
#
#- name: validate results
# assert:
# that:
# - item.finished == 1
# - item.slept_sec == 3
# - item.changed == true
# - item.ansible_job_id is match('\d+\.\d+')
# with_items: "{{ asyncout.results }}"
# this part of the test is flaky- Windows PIDs are reused aggressively, so this occasionally fails due to a new process with the same ID # this part of the test is flaky- Windows PIDs are reused aggressively, so this occasionally fails due to a new process with the same ID
# FUTURE: consider having the test module hook to a kernel object we can poke at that gets signaled/released on exit # FUTURE: consider having the test module hook to a kernel object we can poke at that gets signaled/released on exit