Normal Description
We are seeing lots of warnings like the following:
C:/jenkins/workspace/platform_aio-puppet_unit-ruby_stable-windows/RUBY/ruby-2.1.5.2-x64/SLAVE/unit-win2012/lib/puppet/pops/loader/../../../puppet/functions/defined.rb:71: warning: already initialized constant Puppet::Pops::Loader::RubyFunctionInstantiator::ARG_TYPE
|
Seems to be an order dependent issue. I can reproduce on OSX with:
$ bundle exec rspec spec/integration/parser/class_spec.rb
|
Run options: exclude {:broken=>true, :benchmark=>true}
|
./Users/josh/work/puppet/lib/puppet/pops/loader/../../../puppet/functions/defined.rb:71: warning: already initialized constant Puppet::Pops::Loader::RubyFunctionInstantiator::ARG_TYPE
|
/Users/josh/work/puppet/lib/puppet/pops/loader/../../../puppet/functions/defined.rb:71: warning: previous definition of ARG_TYPE was here
|
./Users/josh/work/puppet/lib/puppet/pops/loader/../../../puppet/functions/defined.rb:71: warning: already initialized constant Puppet::Pops::Loader::RubyFunctionInstantiator::ARG_TYPE
|
However, when running all specs locally I don't see the issue, so there must be some other test that when run first, prevents the warning from being generated.
I'm guessing it's related to how some specs do extend PuppetSpec::Language