<p dir="auto">On the v2.0.0-0.3.beta1 tag I'm currently getting abnormally large task timings (all appear slightly different but start with <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/ansible/ansible/commit/14472405efedf1a7acfdd681f698ff07a9155b84/hovercard" href="https://github.com/ansible/ansible/commit/14472405efedf1a7acfdd681f698ff07a9155b84"><tt>1447240</tt></a>...):</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="2015-11-11 11:32:28,585 p=6905 u=vagrant |  TASK: Task 1 ------------------------1447240566.82s
2015-11-11 11:32:28,586 p=6905 u=vagrant |  TASK: Task 2 ----------------------- 1447240365.34s
2015-11-11 11:32:28,586 p=6905 u=vagrant |  TASK: Task 3 ----------------------- 1447240335.68s
2015-11-11 11:32:28,586 p=6905 u=vagrant |  TASK: Task 4 ----------------------- 95.47s"><pre class="notranslate"><code class="notranslate">2015-11-11 11:32:28,585 p=6905 u=vagrant |  TASK: Task 1 ------------------------1447240566.82s
2015-11-11 11:32:28,586 p=6905 u=vagrant |  TASK: Task 2 ----------------------- 1447240365.34s
2015-11-11 11:32:28,586 p=6905 u=vagrant |  TASK: Task 3 ----------------------- 1447240335.68s
2015-11-11 11:32:28,586 p=6905 u=vagrant |  TASK: Task 4 ----------------------- 95.47s
</code></pre></div>
<p dir="auto">However some of the tasks do appear to log an accurate time. I'm running in CentOS 6.7. I've been unable to identify a pattern in terms of if it is related to a specific module or action for a given task. It almost appears to be random. Wondering if anyone else has seen this on the Dev branch?</p>
<p dir="auto">Issue Type: Bug Report (2.0 regression)<br>
Ansible Version: 2.0.0 (rc1)<br>
Ansible Configuration: default<br>
Environment: NA<br>
Summary: For 1.9 callback plugins, playbook_on_stats was only called once at the end of the playbook run, regardless of number of plays. This made it effectively useful as an "on playbook finish" callback. In 2.0, playbook_on_stats is called at the end of every play, which breaks accumulator-style callbacks.</p>
<p dir="auto">Steps To Reproduce:<br>
Grab sample callback plugin from <a href="https://gist.github.com/nitzmahone/90a2510226f42c7f6e49">https://gist.github.com/nitzmahone/90a2510226f42c7f6e49</a>, drop into callback_plugins. Run test_play.yml from same gist.</p>
<p dir="auto">Expected Results:</p>
<p dir="auto">ON STATS! should show up only once at the end of the playbook run (as it does in 1.9).</p>
<p dir="auto">Actual Results:</p>
<p dir="auto">ON STATS! shows up at the end of each play.</p>
<p dir="auto">Filed on behalf of Callfire</p>