Skip to content

Use a more expressive method of rewriting values #335

Use a more expressive method of rewriting values

Use a more expressive method of rewriting values #335

Triggered via pull request April 2, 2024 12:47
Status Cancelled
Total duration 8m 17s
Artifacts

ci.yml

on: pull_request
Puppet  /  Static validations
29s
Puppet / Static validations
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet  /  Test suite
0s
Puppet / Test suite
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 9 warnings
Puppet / 7 (Ruby 2.7): spec/unit/puppet/type/rabbitmq_parameter_spec.rb#L46
Puppet::Type::Rabbitmq_parameter accepts a valid hash for value Failure/Error: expect(parameter[:value]).to eq(value) expected: {"message-ttl"=>"1800000"} got: {"message-ttl"=>1800000} (compared using ==) Diff: @@ -1 +1 @@ -"message-ttl" => "1800000", +"message-ttl" => 1800000,
Puppet / 7 (Ruby 2.7): spec/unit/puppet/type/rabbitmq_parameter_spec.rb#L70
Puppet::Type::Rabbitmq_parameter accepts array as myparameter Failure/Error: value.transform_values { |v| v.match?(%r{\A[-+]?[0-9]+\z}) ? v.to_i : v } Puppet::ResourceError: Parameter value failed on Rabbitmq_parameter[documentumShovel@/]: Munging failed for value {"myparameter"=>["my", "string"]} in class value: undefined method `match?' for ["my", "string"]:Array
Puppet / 7 (Ruby 2.7)
Process completed with exit code 1.
Puppet / 7 - Ubuntu 18.04
Canceling since a higher priority waiting request for '975/merge' exists
Puppet / 7 - Ubuntu 18.04
The operation was canceled.
Puppet / 7 - Debian 10
Canceling since a higher priority waiting request for '975/merge' exists
Puppet / 7 - Debian 10
The operation was canceled.
Puppet / 7 - CentOS 7: spec/acceptance/class_spec.rb#L130
rabbitmq class: binding on all interfaces Port "25672" Is on 55672 instead on older rmq versions Skipped: Temporarily skipped with xit
Puppet / 7 - CentOS 7: spec/acceptance/class_spec.rb#L165
rabbitmq class: binding to localhost only Port "25672" Is on 55672 instead on older rmq versions Skipped: Temporarily skipped with xit
Puppet / 7 - CentOS 7: spec/acceptance/class_spec.rb#L230
rabbitmq class: different management_ip_address and node_ip_address Port "25672" Is on 55672 instead on older rmq versions Skipped: Temporarily skipped with xit
Puppet / 7 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L130
rabbitmq class: binding on all interfaces Port "25672" Is on 55672 instead on older rmq versions Skipped: Temporarily skipped with xit
Puppet / 7 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L165
rabbitmq class: binding to localhost only Port "25672" Is on 55672 instead on older rmq versions Skipped: Temporarily skipped with xit
Puppet / 7 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L230
rabbitmq class: different management_ip_address and node_ip_address Port "25672" Is on 55672 instead on older rmq versions Skipped: Temporarily skipped with xit
Puppet / 7 - Debian 10: spec/acceptance/class_spec.rb#L130
rabbitmq class: binding on all interfaces Port "25672" Is on 55672 instead on older rmq versions Skipped: Temporarily skipped with xit
Puppet / 7 - Debian 10: spec/acceptance/class_spec.rb#L165
rabbitmq class: binding to localhost only Port "25672" Is on 55672 instead on older rmq versions Skipped: Temporarily skipped with xit
Puppet / 7 - Debian 10: spec/acceptance/class_spec.rb#L230
rabbitmq class: different management_ip_address and node_ip_address Port "25672" Is on 55672 instead on older rmq versions Skipped: Temporarily skipped with xit