Skip to content

Update from voxpupuli modulesync_config #12

Update from voxpupuli modulesync_config

Update from voxpupuli modulesync_config #12

Triggered via pull request July 31, 2024 19:22
Status Failure
Total duration 36s
Artifacts

ci.yml

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

Annotations

5 errors
Puppet / Static validations: spec/support/acceptance/cmdline.rb#L4
RSpec/BeforeAfterAll: Beware of using `before(:context)` as it may cause state to leak between tests. If you are using `rspec-rails`, and `use_transactional_fixtures` is enabled, then records created in `before(:context)` are not automatically rolled back. (https://rspec.rubystyle.guide/#avoid-hooks-with-context-scope, https://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/BeforeAfterAll)
Puppet / Static validations: spec/support/acceptance/cmdline.rb#L10
RSpec/BeforeAfterAll: Beware of using `after(:context)` as it may cause state to leak between tests. If you are using `rspec-rails`, and `use_transactional_fixtures` is enabled, then records created in `after(:context)` are not automatically rolled back. (https://rspec.rubystyle.guide/#avoid-hooks-with-context-scope, https://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/BeforeAfterAll)
Puppet / Static validations: spec/support/acceptance/config.rb#L4
RSpec/BeforeAfterAll: Beware of using `before(:context)` as it may cause state to leak between tests. If you are using `rspec-rails`, and `use_transactional_fixtures` is enabled, then records created in `before(:context)` are not automatically rolled back. (https://rspec.rubystyle.guide/#avoid-hooks-with-context-scope, https://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/BeforeAfterAll)
Puppet / Static validations: spec/support/acceptance/config.rb#L8
RSpec/BeforeAfterAll: Beware of using `after(:context)` as it may cause state to leak between tests. If you are using `rspec-rails`, and `use_transactional_fixtures` is enabled, then records created in `after(:context)` are not automatically rolled back. (https://rspec.rubystyle.guide/#avoid-hooks-with-context-scope, https://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/BeforeAfterAll)
Puppet / Static validations
Process completed with exit code 1.