Thursday, 2019-07-25

*** ricolin has joined #openstack-mistral00:55
*** gkadam has joined #openstack-mistral04:08
*** gkadam has quit IRC04:09
*** eyalb1 has joined #openstack-mistral05:48
*** pgaxatte has joined #openstack-mistral06:48
*** apetrich has quit IRC07:00
*** apetrich has joined #openstack-mistral08:24
*** apetrich has quit IRC08:53
*** eyalb has joined #openstack-mistral08:54
*** eyalb1 has quit IRC08:57
*** jtomasek has joined #openstack-mistral09:01
*** apetrich has joined #openstack-mistral09:02
*** apetrich has quit IRC09:42
openstackgerritEyal proposed openstack/mistral master: When installing devstack enable the bash completion  https://review.opendev.org/67191411:10
*** apetrich has joined #openstack-mistral11:58
*** vgvoleg has joined #openstack-mistral12:24
pgaxattehello12:58
pgaxatteI have a DSL question about retry loops12:58
pgaxatteI have something similar to this:12:58
pgaxattetest_loop:12:58
pgaxatte  action: myaction param1=hello param2=world12:58
pgaxatte  retry:12:58
pgaxatte    delay: 512:58
pgaxatte    count: 1012:58
pgaxatte    continue-on: <% some_condition(task().result) %>12:58
pgaxatte    break-on: <% some_other_condition(task().result) %>12:58
pgaxatteand it does not work as expected12:59
pgaxatteI am wondering if using task().result in a retry loop does what I need12:59
pgaxatteis it evaluated after the task is completed, meaning the loop has ended? or is it evaluated after each action call in the loop?12:59
vgvolegIt should be for each action call13:00
pgaxatteok something else is failing in my conditions13:01
vgvolegI'm not sure how it works in code, but logically the behavior should be for each action call13:01
pgaxattebut task().result seems to return {}13:02
pgaxattewell I don't know, its name is task().result, not action().result13:02
pgaxatteso it makes sense if it is only evaluated after the loop has completed13:02
pgaxattebut then the continue-on and break-on could not use the result of the last action that was run13:03
pgaxatteso I don't know :)13:03
vgvolegI'm not sure what your action can return besides :D13:03
pgaxattei am avoiding to do this by replacing the action with a sub-workflow that does the logic for me and succeeds/fails on my conditions13:04
pgaxattethis way I don't have a continue-on/break-on13:05
*** ricolin has quit IRC13:36
*** apetrich has quit IRC13:43
*** apetrich has joined #openstack-mistral13:47
*** eyalb1 has joined #openstack-mistral13:52
*** eyalb has quit IRC13:54
*** eyalb1 has quit IRC14:21
*** bobh has joined #openstack-mistral14:23
*** ricolin has joined #openstack-mistral15:22
*** pgaxatte has quit IRC15:25
*** ricolin_ has joined #openstack-mistral15:33
*** ricolin has quit IRC15:36
*** ricolin_ is now known as ricolin15:38
*** altlogbot_2 has quit IRC15:48
*** altlogbot_0 has joined #openstack-mistral15:50
*** ricolin has quit IRC16:39
*** bobh has quit IRC17:39
openstackgerritguang-yee proposed openstack/mistral stable/rocky: disable triggering version discovery in test_generator unit tests  https://review.opendev.org/67218517:42
*** jtomasek has quit IRC18:01
*** bobh has joined #openstack-mistral18:11
*** bobh has quit IRC18:17
*** bobh has joined #openstack-mistral19:05
*** bobh has quit IRC19:11
*** bobh has joined #openstack-mistral20:53
*** bobh has quit IRC20:59
*** vgvoleg has quit IRC21:08
openstackgerritguang-yee proposed openstack/mistral stable/rocky: disable triggering version discovery in test_generator unit tests  https://review.opendev.org/67218523:30

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!