*** ricolin has joined #openstack-mistral | 00:55 | |
*** gkadam has joined #openstack-mistral | 04:08 | |
*** gkadam has quit IRC | 04:09 | |
*** eyalb1 has joined #openstack-mistral | 05:48 | |
*** pgaxatte has joined #openstack-mistral | 06:48 | |
*** apetrich has quit IRC | 07:00 | |
*** apetrich has joined #openstack-mistral | 08:24 | |
*** apetrich has quit IRC | 08:53 | |
*** eyalb has joined #openstack-mistral | 08:54 | |
*** eyalb1 has quit IRC | 08:57 | |
*** jtomasek has joined #openstack-mistral | 09:01 | |
*** apetrich has joined #openstack-mistral | 09:02 | |
*** apetrich has quit IRC | 09:42 | |
openstackgerrit | Eyal proposed openstack/mistral master: When installing devstack enable the bash completion https://review.opendev.org/671914 | 11:10 |
---|---|---|
*** apetrich has joined #openstack-mistral | 11:58 | |
*** vgvoleg has joined #openstack-mistral | 12:24 | |
pgaxatte | hello | 12:58 |
pgaxatte | I have a DSL question about retry loops | 12:58 |
pgaxatte | I have something similar to this: | 12:58 |
pgaxatte | test_loop: | 12:58 |
pgaxatte | action: myaction param1=hello param2=world | 12:58 |
pgaxatte | retry: | 12:58 |
pgaxatte | delay: 5 | 12:58 |
pgaxatte | count: 10 | 12:58 |
pgaxatte | continue-on: <% some_condition(task().result) %> | 12:58 |
pgaxatte | break-on: <% some_other_condition(task().result) %> | 12:58 |
pgaxatte | and it does not work as expected | 12:59 |
pgaxatte | I am wondering if using task().result in a retry loop does what I need | 12:59 |
pgaxatte | is 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 |
vgvoleg | It should be for each action call | 13:00 |
pgaxatte | ok something else is failing in my conditions | 13:01 |
vgvoleg | I'm not sure how it works in code, but logically the behavior should be for each action call | 13:01 |
pgaxatte | but task().result seems to return {} | 13:02 |
pgaxatte | well I don't know, its name is task().result, not action().result | 13:02 |
pgaxatte | so it makes sense if it is only evaluated after the loop has completed | 13:02 |
pgaxatte | but then the continue-on and break-on could not use the result of the last action that was run | 13:03 |
pgaxatte | so I don't know :) | 13:03 |
vgvoleg | I'm not sure what your action can return besides :D | 13:03 |
pgaxatte | i am avoiding to do this by replacing the action with a sub-workflow that does the logic for me and succeeds/fails on my conditions | 13:04 |
pgaxatte | this way I don't have a continue-on/break-on | 13:05 |
*** ricolin has quit IRC | 13:36 | |
*** apetrich has quit IRC | 13:43 | |
*** apetrich has joined #openstack-mistral | 13:47 | |
*** eyalb1 has joined #openstack-mistral | 13:52 | |
*** eyalb has quit IRC | 13:54 | |
*** eyalb1 has quit IRC | 14:21 | |
*** bobh has joined #openstack-mistral | 14:23 | |
*** ricolin has joined #openstack-mistral | 15:22 | |
*** pgaxatte has quit IRC | 15:25 | |
*** ricolin_ has joined #openstack-mistral | 15:33 | |
*** ricolin has quit IRC | 15:36 | |
*** ricolin_ is now known as ricolin | 15:38 | |
*** altlogbot_2 has quit IRC | 15:48 | |
*** altlogbot_0 has joined #openstack-mistral | 15:50 | |
*** ricolin has quit IRC | 16:39 | |
*** bobh has quit IRC | 17:39 | |
openstackgerrit | guang-yee proposed openstack/mistral stable/rocky: disable triggering version discovery in test_generator unit tests https://review.opendev.org/672185 | 17:42 |
*** jtomasek has quit IRC | 18:01 | |
*** bobh has joined #openstack-mistral | 18:11 | |
*** bobh has quit IRC | 18:17 | |
*** bobh has joined #openstack-mistral | 19:05 | |
*** bobh has quit IRC | 19:11 | |
*** bobh has joined #openstack-mistral | 20:53 | |
*** bobh has quit IRC | 20:59 | |
*** vgvoleg has quit IRC | 21:08 | |
openstackgerrit | guang-yee proposed openstack/mistral stable/rocky: disable triggering version discovery in test_generator unit tests https://review.opendev.org/672185 | 23:30 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!