Information about some log files

[stappersg]

stappers@myhost:~/src/stappers/infra/warpgate-issue-459/results/ansible_log_broken_pipe
$ file ansible.log-run*
ansible.log-run1: ASCII text, with very long lines (19322)
ansible.log-run2: ASCII text, with very long lines (17386)
stappers@myhost:~/src/stappers/infra/warpgate-issue-459/results/ansible_log_broken_pipe
$ wc ansible.log-run*
   497  11317 142393 ansible.log-run1
   497  18283 236200 ansible.log-run2
   994  29600 378593 totaal
stappers@myhost:~/src/stappers/infra/warpgate-issue-459/results/ansible_log_broken_pipe
$ grep --count --ignore-case broken ansible.log-run*
ansible.log-run1:10
ansible.log-run2:0
stappers@myhost:~/src/stappers/infra/warpgate-issue-459/results/ansible_log_broken_pipe
$ 

Please tell more about those ansible run logs. Especially on possible causes for broken pipes in one run and none in the other run.

Suggested place for the information is a README.md in the results/ansible_log_broken_pipe directory.

( Cross reference to warp-tech/warpgate#479 )

[ntimo]

@stappersg I honestly have no idea where the broken pipes come from.
I run Ansible twice in a row and only the first "fast" run contains the broken pipes which is strange indeed. I am now running Ansible 50 times again to test if they appear in later runs.
If I find some kind of pattern I will create a README.md in the suggested directory.

[ntimo]

Okay only the first run has the broken pipes all other runs have 0.

Which is strange considering that the first one is always faster then the other ones.