Jira (PUP-2827) Don't update lastrunreport and lastrunsummary in noop

[Josh Cooper (Jira)]

Title: Message Title

Josh Cooper updated an issue   Puppet / PUP-2827 Don't update lastrunreport and lastrunsummary in noop Change By: Josh Cooper t.pp -- {code:puppet} node default { } {code} running ```puppet apply --noop t.pp``` Running under 3.6.2 returns 1 with the following errors: {noformat} Error: Failed to apply catalog: Operation not permitted - /var/lib/jenkins/.puppet/var/state/state.yaml20140624-3338-egqchx Error: Could not save last run local report: Operation not permitted - /var/lib/jenkins/.puppet/var/state/last_run_summary.yaml20140624-3338-187sv5a Error: Could not send report: Operation not permitted - /var/lib/jenkins/.puppet/var/state/last_run_report.yaml20140624-3338-djuxtb Running under 3.2.4 returns 0 with following output: Notice: Finished catalog run in 1.93 seconds {noformat} If this change was/is desired behaviour (not to us, but perhaps that decision was made), would be great to have an additional flag to turn off that behaviour for automated testing. Add Comment   This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.40211.1403613158000.56751.1588863720030%40Atlassian.JIRA.