Issue #4865 has been updated by Trevor Vaughan.
I just took a look at the patch. Wouldn't it be better to have that output at the info rather than debug level? If you're doing --evaltrace you're looking for timing data so this would be useful in my opinion. Debug is just too noisy when all you want is to see where something is hanging quickly. ---------------------------------------- Feature #4865: Puppet debug mode should print resource type/title before resource evaluation and time taken after. https://projects.puppetlabs.com/issues/4865 Author: James Turnbull Status: In Topic Branch Pending Review Priority: High Assignee: Daniel Pittman Category: error reporting Target version: 2.7.x Affected Puppet version: 2.6.1 Keywords: usability Branch: https://github.com/puppetlabs/puppet/pull/202 1) Only on the client 2) Time taken during each atomic activity So: notice: File....... 0.05s notice: Exec...... 1.2s Ideally, this data would only be collected during debug mode. This is for the case where you have something hanging, but you can't figure out what it is because the debug mode in puppet only prints the statement *after* it has run it. This would let everyone determine the hang points, or points of precise optimization. If there's already a way to get this information, that would be great too. --summarize just isn't quite fine grained enough. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
