Bug #3104

Test failed: Puppet::Network::XMLRPCClient when performing the rpc call and an exception is raised.should log and raise XMLRPCClientError if Timeout::Error is raised

Added by James Turnbull 6 months ago. Updated 6 months ago.

Status:Closed Start:01/24/2010
Priority:Normal Due date:
Assigned to:Markus Roberts % Done:

0%
Category:testing
Target version:0.25.4
Affected version:0.25.4rc3 Branch:http://github.com/MarkusQ/puppet/tree/ticket/0.25.x/3104
Keywords:
Votes: 0

Description

Puppet::Network::XMLRPCClient when performing the rpc call and an exception is raised.should log and raise XMLRPCClientError if Timeout::Error is raised
Failing for the past 1 build (Since Failed#9 )
Took 54 ms.
add description
Error Message

expected Puppet::Network::XMLRPCClientError, got #

Stacktrace

expected Puppet::Network::XMLRPCClientError, got # (Spec::Expectations::ExpectationNotMetError)
./spec/unit/network/xmlrpc/client.rb:99
./spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:22:in `run'
./spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in `each'
./spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in `run'

History

Updated by Markus Roberts 6 months ago

  • Status changed from Investigating to Accepted

This was caused by the fix for #3088 combined with the fact that, in ruby’s wonderful Exception hierarchy, Timeout::error descends from both SignalException and Interrupt. The solution is a partial reversion of the #3088 patch to remove these.

Updated by Markus Roberts 6 months ago

  • Status changed from Accepted to Ready for Testing
  • Affected version changed from 0.25.3 to 0.25.4rc3
  • Branch set to http://github.com/MarkusQ/puppet/tree/ticket/0.25.x/3104

Updated by James Turnbull 6 months ago

  • Status changed from Ready for Testing to Closed

Pushed in commit:“0025e13792b6a8e010ce1fd1dc20a17e7ba8af53” in branch 0.25.x

Also available in: Atom PDF