Update dependency puppetlabs-ruby_task_helper to v1 #1026
renovate[bot]tests.yaml
on: pull_request
rubocop_and_matrix
53s
Linux: Generate module cache
23s
Windows: Generate module cache
4m 41s
Matrix: modules_ci
run-dita
1m 2s
Matrix: Docker Transport
Matrix: Linux Integration
Matrix: SSH Transport
Matrix: bolt apply
Matrix: local_transports
Matrix: unit
Matrix: BoltSpec
Matrix: Windows Agentless
Matrix: Windows Integration
Matrix: WinRM Transport
Test suite
3s
Annotations
4 errors and 67 warnings
|
Check mod deps
Process completed with exit code 3.
|
|
Windows Integration (3.4)
Process completed with exit code 1.
|
|
Windows Integration (3.4):
spec/integration/winrm_spec.rb#L239
when runnning over the winrm transport when using an inventoryfile script interpreter without future.script_interpreter configured does not run script with specified interpreter
Failure/Error: expect(result['status']).to eq('success')
expected: "success"
got: "failure"
(compared using ==)
|
|
Test suite
Process completed with exit code 1.
|
|
rubocop_and_matrix
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/
|
|
Unit tests 3.4 ubuntu-24.04:
spec/unit/analytics_spec.rb#L101
Bolt::Analytics config file falls back to the default project directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 ubuntu-24.04:
spec/unit/analytics_spec.rb#L92
Bolt::Analytics config file loads config from user-level config directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 ubuntu-24.04:
spec/unit/analytics_spec.rb#L78
Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 ubuntu-24.04:
spec/unit/analytics_spec.rb#L69
Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 ubuntu-24.04:
spec/unit/analytics_spec.rb#L53
Bolt::Analytics assigns the user a uuid if one doesn't exist
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 ubuntu-24.04:
spec/unit/analytics_spec.rb#L46
Bolt::Analytics uses the uuid in the config if it exists
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 ubuntu-24.04:
spec/unit/analytics_spec.rb#L42
Bolt::Analytics creates a regular Client if analytics is not disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 ubuntu-24.04:
spec/unit/analytics_spec.rb#L31
Bolt::Analytics creates a NoopClient if reading config fails
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 ubuntu-24.04:
spec/unit/analytics_spec.rb#L26
Bolt::Analytics creates a NoopClient if analytics is disabled in config
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 ubuntu-24.04:
spec/unit/analytics_spec.rb#L19
Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 ubuntu-24.04:
spec/unit/analytics_spec.rb#L101
Bolt::Analytics config file falls back to the default project directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 ubuntu-24.04:
spec/unit/analytics_spec.rb#L92
Bolt::Analytics config file loads config from user-level config directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 ubuntu-24.04:
spec/unit/analytics_spec.rb#L78
Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 ubuntu-24.04:
spec/unit/analytics_spec.rb#L69
Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 ubuntu-24.04:
spec/unit/analytics_spec.rb#L53
Bolt::Analytics assigns the user a uuid if one doesn't exist
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 ubuntu-24.04:
spec/unit/analytics_spec.rb#L46
Bolt::Analytics uses the uuid in the config if it exists
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 ubuntu-24.04:
spec/unit/analytics_spec.rb#L42
Bolt::Analytics creates a regular Client if analytics is not disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 ubuntu-24.04:
spec/unit/analytics_spec.rb#L31
Bolt::Analytics creates a NoopClient if reading config fails
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 ubuntu-24.04:
spec/unit/analytics_spec.rb#L26
Bolt::Analytics creates a NoopClient if analytics is disabled in config
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 ubuntu-24.04:
spec/unit/analytics_spec.rb#L19
Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 ubuntu-24.04:
spec/unit/analytics_spec.rb#L101
Bolt::Analytics config file falls back to the default project directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 ubuntu-24.04:
spec/unit/analytics_spec.rb#L92
Bolt::Analytics config file loads config from user-level config directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 ubuntu-24.04:
spec/unit/analytics_spec.rb#L78
Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 ubuntu-24.04:
spec/unit/analytics_spec.rb#L69
Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 ubuntu-24.04:
spec/unit/analytics_spec.rb#L53
Bolt::Analytics assigns the user a uuid if one doesn't exist
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 ubuntu-24.04:
spec/unit/analytics_spec.rb#L46
Bolt::Analytics uses the uuid in the config if it exists
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 ubuntu-24.04:
spec/unit/analytics_spec.rb#L42
Bolt::Analytics creates a regular Client if analytics is not disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 ubuntu-24.04:
spec/unit/analytics_spec.rb#L31
Bolt::Analytics creates a NoopClient if reading config fails
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 ubuntu-24.04:
spec/unit/analytics_spec.rb#L26
Bolt::Analytics creates a NoopClient if analytics is disabled in config
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 ubuntu-24.04:
spec/unit/analytics_spec.rb#L19
Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file
Skipped: Analytics is currently disabled
|
|
Windows Agentless (3.2):
spec/integration/apply_error_spec.rb#L56
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
|
|
Windows Agentless (3.4):
spec/integration/apply_error_spec.rb#L56
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
|
|
Unit tests 3.2 windows-2025:
spec/unit/analytics_spec.rb#L101
Bolt::Analytics config file falls back to the default project directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 windows-2025:
spec/unit/analytics_spec.rb#L92
Bolt::Analytics config file loads config from user-level config directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 windows-2025:
spec/unit/analytics_spec.rb#L78
Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 windows-2025:
spec/unit/analytics_spec.rb#L69
Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 windows-2025:
spec/unit/analytics_spec.rb#L53
Bolt::Analytics assigns the user a uuid if one doesn't exist
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 windows-2025:
spec/unit/analytics_spec.rb#L46
Bolt::Analytics uses the uuid in the config if it exists
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 windows-2025:
spec/unit/analytics_spec.rb#L42
Bolt::Analytics creates a regular Client if analytics is not disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 windows-2025:
spec/unit/analytics_spec.rb#L31
Bolt::Analytics creates a NoopClient if reading config fails
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 windows-2025:
spec/unit/analytics_spec.rb#L26
Bolt::Analytics creates a NoopClient if analytics is disabled in config
Skipped: Analytics is currently disabled
|
|
Unit tests 3.2 windows-2025:
spec/unit/analytics_spec.rb#L19
Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 windows-2025:
spec/unit/analytics_spec.rb#L101
Bolt::Analytics config file falls back to the default project directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 windows-2025:
spec/unit/analytics_spec.rb#L92
Bolt::Analytics config file loads config from user-level config directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 windows-2025:
spec/unit/analytics_spec.rb#L78
Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 windows-2025:
spec/unit/analytics_spec.rb#L69
Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 windows-2025:
spec/unit/analytics_spec.rb#L53
Bolt::Analytics assigns the user a uuid if one doesn't exist
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 windows-2025:
spec/unit/analytics_spec.rb#L46
Bolt::Analytics uses the uuid in the config if it exists
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 windows-2025:
spec/unit/analytics_spec.rb#L42
Bolt::Analytics creates a regular Client if analytics is not disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 windows-2025:
spec/unit/analytics_spec.rb#L31
Bolt::Analytics creates a NoopClient if reading config fails
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 windows-2025:
spec/unit/analytics_spec.rb#L26
Bolt::Analytics creates a NoopClient if analytics is disabled in config
Skipped: Analytics is currently disabled
|
|
Unit tests 3.4 windows-2025:
spec/unit/analytics_spec.rb#L19
Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file
Skipped: Analytics is currently disabled
|
|
local transport 3.2 windows-2025:
spec/shared_examples/transport.rb#L562
Bolt::Transport::Local when tmpdir is specified errors when tmpdir doesn't exist
Skipped: Windows will create the directory anyway
|
|
local transport 3.4 windows-2025:
spec/shared_examples/transport.rb#L562
Bolt::Transport::Local when tmpdir is specified errors when tmpdir doesn't exist
Skipped: Windows will create the directory anyway
|
|
Windows Agentless (3.3):
spec/integration/apply_error_spec.rb#L56
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
|
|
local transport 3.3 windows-2025:
spec/shared_examples/transport.rb#L562
Bolt::Transport::Local when tmpdir is specified errors when tmpdir doesn't exist
Skipped: Windows will create the directory anyway
|
|
Unit tests 3.3 windows-2025:
spec/unit/analytics_spec.rb#L101
Bolt::Analytics config file falls back to the default project directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 windows-2025:
spec/unit/analytics_spec.rb#L92
Bolt::Analytics config file loads config from user-level config directory
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 windows-2025:
spec/unit/analytics_spec.rb#L78
Bolt::Analytics without analytics.yaml does not warn when running with analytics disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 windows-2025:
spec/unit/analytics_spec.rb#L69
Bolt::Analytics without analytics.yaml warns when running with analytics enabled for the first time
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 windows-2025:
spec/unit/analytics_spec.rb#L53
Bolt::Analytics assigns the user a uuid if one doesn't exist
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 windows-2025:
spec/unit/analytics_spec.rb#L46
Bolt::Analytics uses the uuid in the config if it exists
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 windows-2025:
spec/unit/analytics_spec.rb#L42
Bolt::Analytics creates a regular Client if analytics is not disabled
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 windows-2025:
spec/unit/analytics_spec.rb#L31
Bolt::Analytics creates a NoopClient if reading config fails
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 windows-2025:
spec/unit/analytics_spec.rb#L26
Bolt::Analytics creates a NoopClient if analytics is disabled in config
Skipped: Analytics is currently disabled
|
|
Unit tests 3.3 windows-2025:
spec/unit/analytics_spec.rb#L19
Bolt::Analytics creates a NoopClient if analytics is disabled in analytics file
Skipped: Analytics is currently disabled
|