semaphore
semaphore copied to clipboard
Output in random order
I ran a playbook in debug mode and closed the console while the playbook was running. After the playbook was done, I opened the console output again. The lines were roughly following the flow, but a few lines were in random order. The playbook generates a large amount of output lines because some local variables are created. The variables contain over 50 elements.
In the screenshot you can see that after the summary there are more lines that actually belong to another task.
I'm not entirely sure I have the same behavior, however, in my case, I have sometimes the debug stdout_lines inverted in order. Normally when I register on a variable a win_shell output. Any clue? Not able to understand why
You can see the wrong sequence. The number shows how it is supposed to appear if the script is executed locally using win_shell. The playbook save the output of win_shell and prints with debug.