Issue #2877 has been updated by Jesse Wolfe.
This wasn't failing for me, so I started to do a git-bisect to see if it had changed due to a fix. I did manage to reproduce the error during the bisect run, but then when I reran the test on the reported version, it no longer failed! So I wrote a script to step through the git history and test every single commit back to early november ... and it ran without failing a single time. There's something else going on here. I did manage to save the stack trace of the failure: 1) in 'Puppet::Network::Server when using webrick after unlistening should not be reachable on the port and address assigned' execution expired /home/jes5199/Desktop/personal/puerto_haskell/puppet/spec/../lib/puppet/network/http/webrick.rb:52:in `synchronize' /home/jes5199/Desktop/personal/puerto_haskell/puppet/spec/../lib/puppet/network/http/webrick.rb:52:in `unlisten' /home/jes5199/Desktop/personal/puerto_haskell/puppet/lib/puppet/network/server.rb:136:in `unlisten' ./spec/integration/network/server/webrick.rb:81: /home/jes5199/Desktop/personal/puerto_haskell/puppet/spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:22:in `run' /home/jes5199/Desktop/personal/puerto_haskell/puppet/spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in `each' /home/jes5199/Desktop/personal/puerto_haskell/puppet/spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in `run' Apparently that's some sort of timeout. ---------------------------------------- Bug #2877: Test isolation: Spurious failure in spec/integration/network/server/webrick.rb http://projects.reductivelabs.com/issues/2877 Author: Markus Roberts Status: Accepted Priority: Low Assigned to: Jesse Wolfe Category: testing Target version: 0.25.2 Affected version: 0.25.1 Keywords: Branch: When spec/integration/network/server/webrick.rb is run with certain other tests a spurious failure is produced: should not be reachable on the port and address assigned (FAILED - #) The effect has been observed when running the webrick tests before: * spec/integration/file_serving/fileset.rb * spec/integration/network/server/mongrel.rb * spec/unit/type/file/group.rb * spec/unit/rails/host.rb * spec/unit/type/service.rb * spec/unit/parameter.rb * spec/integration/ssl/certificate_request.rb * spec/unit/network/rest_authorization.rb or after: * spec/integration/reference/providers.rb * spec/unit/other/transobject.rb * spec/unit/indirector/memory.rb * spec/unit/type/noop_metaparam.rb * spec/unit/node.rb * spec/unit/type/filebucket.rb There are probably other confounding factors; at least, I can't come up with a plausible model to explain the observed effects. To reproduce: touch spec/integration/network/server/webrick.rb ruby spec/integration/network/server/webrick.rb spec/integration/file_serving/fileset.rb -t 60 --format s --loadby mtime -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
