The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #13895

Spec tests should not actually pluginsync

Added by Josh Cooper over 2 years ago. Updated over 2 years ago.

Status:AcceptedStart date:04/11/2012
Priority:NormalDue date:
Assignee:Jeff McCune% Done:

0%

Category:testing
Target version:3.x
Affected Puppet version:development Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

Several of the spec tests in the master branch now attempt to make a TCP connection to puppet (since pluginsync is now enabled by default). The spec tests in 2.7.x do not have this problem:

rspec -fd spec/integration/configurer_spec.rb
$ ps -ef | grep ruby
  502  8902   308   0   0:00.11 ttys000    0:00.55 /Users/josh/.rvm/rubies/ruby-1.8.7-p334/bin/ruby /Users/josh/.rvm/gems/ruby-1.8.7-p334@noFeatures/bin/rspec -fd spec/integration/configurer_spec.rb
...
$ lsof -p 8902
ruby    8902 josh    3u  IPv4 0x0fe20708       0t0      TCP 172.16.138.1:50097->puppet:8140 (SYN_SENT)

For me, the host puppet points to a VM that isn’t running, so the TCP connection takes 2 minutes to time out.


Related issues

Related to Puppet - Bug #15569: Order dependent spec failures Accepted 07/17/2012

History

#1 Updated by Josh Cooper over 2 years ago

  • Assignee changed from Patrick Carlisle to Jeff McCune

Also available in: Atom PDF