Jira (PUP-3081) reported catalog run time is wildly inaccurate

[William Hopper (JIRA)]

Title: Message Title

William Hopper commented on an issue   Re: reported catalog run time is wildly inaccurate Functional review: verified at SHA 931a1b5b (CentOS 7): On an agent run with a simple test manifest being applied: [root@b23ranzrafqh1q5 ~]# puppet agent -t Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for b23ranzrafqh1q5.delivery.puppetlabs.net Info: Applying configuration version '1413588044' Notice: /Stage[main]/Main/Node[default]/Exec[hello]/returns: executed successfully Notice: Applied catalog in 0.03 seconds As expected, we now see "Applied catalog" instead of "Finished catalog run." Add Comment   Puppet / PUP-3081 reported catalog run time is wildly inaccurate The puppet client clearly does not actually use wallclock time to calculate how long a puppet run takes. Here are a few examples of puppet runs with the time command: # time puppet agent -t .... Notice: Finished catalog run in 131.19 seconds real 3m32.015s user 1m48.207s sys 0m18.101s # time puppet agent -t .... Notice: Fin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.