Build(deps): Bump dita-ot/dita-ot-action from 4.3.5 to 4.4 #928
dependabot[bot]tests.yaml
on: pull_request
rubocop_and_matrix
51s
Linux: Generate module cache
17s
Windows: Generate module cache
1m 7s
Matrix: modules_ci
run-dita
1m 0s
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
4s
Annotations
3 errors and 66 warnings
|
Windows Integration (3.4)
Process completed with exit code 1.
|
|
Windows Integration (3.4):
spec/integration/winrm_spec.rb#L55
when runnning over the winrm transport when using CLI options runs a task reading from environment variables
Failure/Error: expect(result).to eq("Should have succeed on node" => true)
expected: {"Should have succeed on node" => true}
got: {"elapsed_time" => 2, "items" => [{"action" => "task", "object" => nil, "status" => "failure", "target" => "winrm://roddypiper@localhost:5985", "value" => {"_error" => {"details" => {}, "issue_code" => "WRITE_ERROR", "kind" => "puppetlabs.tasks/task_f...om/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>"}}}], "target_count" => 1}
(compared using ==)
Diff:
@@ -1 +1,3 @@
-"Should have succeed on node" => true,
+"elapsed_time" => 2,
+"items" => [{"action" => "task", "object" => nil, "status" => "failure", "target" => "winrm://roddypiper@localhost:5985", "value" => {"_error" => {"details" => {}, "issue_code" => "WRITE_ERROR", "kind" => "puppetlabs.tasks/task_file_error", "msg" => "[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>"}}}],
+"target_count" => 1,
|
|
Test suite
Process completed with exit code 1.
|
|
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.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
|
|
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
|
|
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
|
|
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.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.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.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.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
|
|
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
|