Skip to content

Treat initial-cluster-size option in policy as an integer #238

Treat initial-cluster-size option in policy as an integer

Treat initial-cluster-size option in policy as an integer #238

Triggered via pull request October 31, 2023 04:42
Status Cancelled
Total duration 6m 38s
Artifacts

ci.yml

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

Annotations

8 errors and 6 warnings
Puppet / 7 (Ruby 2.7): spec/unit/puppet/type/rabbitmq_policy_spec.rb#L204
Puppet::Type::Rabbitmq_policy does not accept non-numeric initial-cluster-size value Failure/Error: expect do policy[:definition] = definition end.to raise_error(Puppet::Error, %r{Invalid initial-cluster-size value.*future}) expected Puppet::Error with message matching /Invalid initial-cluster-size value.*future/, got #<Puppet::ResourceError: Parameter definition failed on Rabbitmq_policy[ha-all@/]: Invalid initial-cluster-size value 'impressive'> with backtrace: # ./lib/puppet/type/rabbitmq_policy.rb:129:in `validate_definition' # ./lib/puppet/type/rabbitmq_policy.rb:62:in `block (3 levels) in <top (required)>' # ./vendor/bundle/ruby/2.7.0/gems/puppet-7.26.0/lib/puppet/parameter.rb:478:in `validate' # ./vendor/bundle/ruby/2.7.0/gems/puppet-7.26.0/lib/puppet/property.rb:550:in `block in should=' # ./vendor/bundle/ruby/2.7.0/gems/puppet-7.26.0/lib/puppet/property.rb:550:in `each' # ./vendor/bundle/ruby/2.7.0/gems/puppet-7.26.0/lib/puppet/property.rb:550:in `should=' # ./vendor/bundle/ruby/2.7.0/gems/puppet-7.26.0/lib/puppet/property.rb:609:in `value=' # ./vendor/bundle/ruby/2.7.0/gems/puppet-7.26.0/lib/puppet/type.rb:681:in `[]=' # ./spec/unit/puppet/type/rabbitmq_policy_spec.rb:207:in `block (3 levels) in <top (required)>' # ./spec/unit/puppet/type/rabbitmq_policy_spec.rb:206:in `block (2 levels) in <top (required)>'
Puppet / 7 (Ruby 2.7)
Process completed with exit code 1.
Puppet / 7 - Debian 10
Canceling since a higher priority waiting request for '950/merge' exists
Puppet / 7 - Debian 10
The operation was canceled.
Puppet / 7 - CentOS 7
Canceling since a higher priority waiting request for '950/merge' exists
Puppet / 7 - CentOS 7
The operation was canceled.
Puppet / 7 - Ubuntu 18.04
Canceling since a higher priority waiting request for '950/merge' exists
Puppet / 7 - Ubuntu 18.04
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