You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Darryl L. Pierce (JIRA)" <ji...@apache.org> on 2013/07/16 15:02:48 UTC
[jira] [Resolved] (PROTON-355) Fix broken Ruby Rspec tests
[ https://issues.apache.org/jira/browse/PROTON-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darryl L. Pierce resolved PROTON-355.
-------------------------------------
Resolution: Fixed
Fixed in the following commit:
http://svn.apache.org/viewvc?view=revision&revision=1503701
incorrectly marked as QPID-355.
> Fix broken Ruby Rspec tests
> ---------------------------
>
> Key: PROTON-355
> URL: https://issues.apache.org/jira/browse/PROTON-355
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.4
> Reporter: Darryl L. Pierce
> Assignee: Darryl L. Pierce
> Fix For: 0.5
>
>
> Currently there are 9 broken tests:
> Failures:
> 1) A data object can hold an array
> Failure/Error: @data.put_array false, Data::INT
> NameError:
> uninitialized constant Qpid::Proton::Data::INT
> # ./spec/qpid/proton/data_spec.rb:417:in `block (2 levels) in <module:Proton>'
> 2) A data object can hold a described array
> Failure/Error: @data.put_array true, Data::STRING
> NameError:
> uninitialized constant Qpid::Proton::Data::STRING
> # ./spec/qpid/proton/data_spec.rb:433:in `block (2 levels) in <module:Proton>'
> 3) A messenger has an error number
> Failure/Error: expect {
> expected Qpid::Proton::ProtonError but nothing was raised
> # ./spec/qpid/proton/messenger_spec.rb:72:in `block (2 levels) in <module:Proton>'
> 4) A messenger has an error message
> Failure/Error: expect {
> expected Qpid::Proton::ProtonError but nothing was raised
> # ./spec/qpid/proton/messenger_spec.rb:83:in `block (2 levels) in <module:Proton>'
> 5) A messenger raises an error when subscribing to an invalid address
> Failure/Error: expect {
> expected Qpid::Proton::ProtonError but nothing was raised
> # ./spec/qpid/proton/messenger_spec.rb:109:in `block (2 levels) in <module:Proton>'
> 6) A messenger once started does not return a tracker before sending messages
> Failure/Error: @messenger.outgoing_tracker.should be_nil
> expected: nil
> got: #<Qpid::Proton::Tracker:0x000000015c1588 @impl=0>
> # ./spec/qpid/proton/messenger_spec.rb:234:in `block (3 levels) in <module:Proton>'
> 7) A messenger once started and subscribed to an address has a nil incoming tracker when no messages are received
> Failure/Error: @messenger.incoming_tracker.should be_nil
> expected: nil
> got: #<Qpid::Proton::Tracker:0x00000001594290 @impl=0>
> # ./spec/qpid/proton/messenger_spec.rb:353:in `block (4 levels) in <module:Proton>'
> 8) A messenger once started and subscribed to an address with a an outgoing tracker raises an error when settling with a nil flag
> Failure/Error: @receiver.stop
> Qpid::Proton::TimeoutError:
> Qpid::Proton::TimeoutError
> # ./lib/qpid_proton/exception_handling.rb:55:in `check_for_error'
> # ./lib/qpid_proton/messenger.rb:115:in `stop'
> # ./spec/qpid/proton/messenger_spec.rb:276:in `block (4 levels) in <module:Proton>'
> 9) A messenger once started and subscribed to an address with messages sent raises an error when receiving with a negative max
> Failure/Error: expect {
> expected RangeError, got #<Qpid::Proton::TimeoutError: Qpid::Proton::TimeoutError> with backtrace:
> # ./lib/qpid_proton/exception_handling.rb:55:in `check_for_error'
> # ./lib/qpid_proton/messenger.rb:232:in `receive'
> # ./spec/qpid/proton/messenger_spec.rb:428:in `block (6 levels) in <module:Proton>'
> # ./spec/qpid/proton/messenger_spec.rb:427:in `block (5 levels) in <module:Proton>'
> # ./spec/qpid/proton/messenger_spec.rb:427:in `block (5 levels) in <module:Proton>'
> Finished in 0.11794 seconds
> 226 examples, 9 failures, 15 pending
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira