Process completed with exit code 1.

installing modules resolving git modules public GitLab source installs the module Failure/Error: raise Bolt::Error.new("Unable to resolve modules: #{e.message}", 'bolt/module-resolver-error') Bolt::Error: Unable to resolve modules: Unable to find module puppetlabs-stdlib on https://forgeapi.puppet.com: Connection reset by peer - SSL_connect

Process completed with exit code 1.

Bolt::Transport::WinRM with an open connection using winrm can upload a directory to a host Failure/Error: result = session.run(command) WinRM::WinRMWSManFault: [WSMAN ERROR CODE: 1018]: <f:WSManFault Code='1018' Machine='localhost' xmlns:f='http://schemas.microsoft.com/wbem/wsman/1/wsmanfault'><f:Message>The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. </f:Message></f:WSManFault>

Process completed with exit code 1.

Bolt::Transport::WinRM with an open connection using winrm can download a directory from a host Failure/Error: raise Bolt::Node::FileError.new(e.message, 'WRITE_ERROR') Bolt::Node::FileError: [WSMAN ERROR CODE: 1018]: <f:WSManFault Code='1018' Machine='localhost' xmlns:f='http://schemas.microsoft.com/wbem/wsman/1/wsmanfault'><f:Message>The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. </f:Message></f:WSManFault>

Bolt::Transport::WinRM with an open connection using winrm can upload a directory to a host Failure/Error: result = session.run(command) WinRM::WinRMWSManFault: [WSMAN ERROR CODE: 1018]: <f:WSManFault Code='1018' Machine='localhost' xmlns:f='http://schemas.microsoft.com/wbem/wsman/1/wsmanfault'><f:Message>The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. </f:Message></f:WSManFault>

Process completed with exit code 1.

Bolt::Transport::WinRM with an open connection when files are provided puts files at _installdir Failure/Error: raise Bolt::Node::FileError.new(e.message, 'WRITE_ERROR') Bolt::Node::FileError: [WSMAN ERROR CODE: 1018]: <f:WSManFault Code='1018' Machine='localhost' xmlns:f='http://schemas.microsoft.com/wbem/wsman/1/wsmanfault'><f:Message>The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. </f:Message></f:WSManFault>

Process completed with exit code 1.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Bolt::Analytics config file falls back to the default project directory Skipped: Analytics is currently disabled

Bolt::Analytics config file loads config from user-level config directory Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time Skipped: Analytics is currently disabled

Bolt::Analytics assigns the user a uuid if one doesn't exist Skipped: Analytics is currently disabled

Bolt::Analytics uses the uuid in the config if it exists Skipped: Analytics is currently disabled

Bolt::Analytics creates a regular Client if analytics is not disabled Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if reading config fails Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in config Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file Skipped: Analytics is currently disabled

Bolt::Analytics config file falls back to the default project directory Skipped: Analytics is currently disabled

Bolt::Analytics config file loads config from user-level config directory Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time Skipped: Analytics is currently disabled

Bolt::Analytics assigns the user a uuid if one doesn't exist Skipped: Analytics is currently disabled

Bolt::Analytics uses the uuid in the config if it exists Skipped: Analytics is currently disabled

Bolt::Analytics creates a regular Client if analytics is not disabled Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if reading config fails Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in config Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file Skipped: Analytics is currently disabled

Bolt::Analytics config file falls back to the default project directory Skipped: Analytics is currently disabled

Bolt::Analytics config file loads config from user-level config directory Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time Skipped: Analytics is currently disabled

Bolt::Analytics assigns the user a uuid if one doesn't exist Skipped: Analytics is currently disabled

Bolt::Analytics uses the uuid in the config if it exists Skipped: Analytics is currently disabled

Bolt::Analytics creates a regular Client if analytics is not disabled Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if reading config fails Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in config Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file Skipped: Analytics is currently disabled

Bolt::Analytics config file falls back to the default project directory Skipped: Analytics is currently disabled

Bolt::Analytics config file loads config from user-level config directory Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time Skipped: Analytics is currently disabled

Bolt::Analytics assigns the user a uuid if one doesn't exist Skipped: Analytics is currently disabled

Bolt::Analytics uses the uuid in the config if it exists Skipped: Analytics is currently disabled

Bolt::Analytics creates a regular Client if analytics is not disabled Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if reading config fails Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in config Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file Skipped: Analytics is currently disabled

errors gracefully attempting to apply a manifest block over winrm prints a helpful error if Puppet is not present Skipped: Skipping this test as it fails with a connection error until #3001 is fixed

Bolt::Transport::Local when tmpdir is specified errors when tmpdir doesn't exist Skipped: Windows will create the directory anyway

Bolt::Analytics config file falls back to the default project directory Skipped: Analytics is currently disabled

Bolt::Analytics config file loads config from user-level config directory Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time Skipped: Analytics is currently disabled

Bolt::Analytics assigns the user a uuid if one doesn't exist Skipped: Analytics is currently disabled

Bolt::Analytics uses the uuid in the config if it exists Skipped: Analytics is currently disabled

Bolt::Analytics creates a regular Client if analytics is not disabled Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if reading config fails Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in config Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file Skipped: Analytics is currently disabled

errors gracefully attempting to apply a manifest block over winrm prints a helpful error if Puppet is not present Skipped: Skipping this test as it fails with a connection error until #3001 is fixed

Bolt::Analytics config file falls back to the default project directory Skipped: Analytics is currently disabled

Bolt::Analytics config file loads config from user-level config directory Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time Skipped: Analytics is currently disabled

Bolt::Analytics assigns the user a uuid if one doesn't exist Skipped: Analytics is currently disabled

Bolt::Analytics uses the uuid in the config if it exists Skipped: Analytics is currently disabled

Bolt::Analytics creates a regular Client if analytics is not disabled Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if reading config fails Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in config Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file Skipped: Analytics is currently disabled

Bolt::Transport::Local when tmpdir is specified errors when tmpdir doesn't exist Skipped: Windows will create the directory anyway

errors gracefully attempting to apply a manifest block over winrm prints a helpful error if Puppet is not present Skipped: Skipping this test as it fails with a connection error until #3001 is fixed

Bolt::Transport::Local when tmpdir is specified errors when tmpdir doesn't exist Skipped: Windows will create the directory anyway

Bolt::Analytics config file falls back to the default project directory Skipped: Analytics is currently disabled

Bolt::Analytics config file loads config from user-level config directory Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time Skipped: Analytics is currently disabled

Bolt::Analytics assigns the user a uuid if one doesn't exist Skipped: Analytics is currently disabled

Bolt::Analytics uses the uuid in the config if it exists Skipped: Analytics is currently disabled

Bolt::Analytics creates a regular Client if analytics is not disabled Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if reading config fails Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in config Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file Skipped: Analytics is currently disabled

errors gracefully attempting to apply a manifest block over winrm prints a helpful error if Puppet is not present Skipped: Skipping this test as it fails with a connection error until #3001 is fixed

Bolt::Analytics config file falls back to the default project directory Skipped: Analytics is currently disabled

Bolt::Analytics config file loads config from user-level config directory Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled Skipped: Analytics is currently disabled

Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time Skipped: Analytics is currently disabled

Bolt::Analytics assigns the user a uuid if one doesn't exist Skipped: Analytics is currently disabled

Bolt::Analytics uses the uuid in the config if it exists Skipped: Analytics is currently disabled

Bolt::Analytics creates a regular Client if analytics is not disabled Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if reading config fails Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in config Skipped: Analytics is currently disabled

Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file Skipped: Analytics is currently disabled