[jira] [Commented] (PROTON-1658) [OSX] ruby-example-test test_tools.rb initialize times out and hangs
[
https://issues.apache.org/jira/browse/PROTON-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254185#comment-16254185
]
ASF subversion and git services commented on PROTON-1658:
-
Commit 738c1980eff65051163e53ba2f1a64a0ce2672dd in qpid-proton's branch
refs/heads/go1 from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=738c198 ]
PROTON-1658: [ruby] simpler, more portable port allocation for tests
The SO_REUSEADDR trick that works on Linux does not work on OSX or Windows.
Use a simpler approach of listen(0), close socket, do real listen. This is
potentially race-prone but works well in practice
The correct solution is to allow the container to listen using a pre-existing
socket,
this is coming with PROTON-1064.
> [OSX] ruby-example-test test_tools.rb initialize times out and hangs
>
>
> Key: PROTON-1658
> URL: https://issues.apache.org/jira/browse/PROTON-1658
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: ruby-binding
> Environment: OSX 10.11.6, Xcode 7.3.1, ruby 2.0.0p648
>Reporter: Roddie Kieley
>Assignee: Alan Conway
> Fix For: proton-c-0.18.1
>
>
> {code}
> test 1
> Start 1: ruby-example-test
> 1: Test command: /usr/bin/ruby "example_test.rb" "-v"
> 1: Environment variables:
> 1:
> PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/Developer/SDKs/android-sdk-mac_x86-1.6_r1:/Developer/SDKs/android-sdk-mac_x86-1.6_r1/tools:/Developer/SDKs/adt-bundle-mac-x86_64/sdk/tools:/Developer/SDKs/adt-bundle-mac-x86_64/sdk/platform-tools:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c
> 1:
> RUBYLIB=:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/lib:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/spec:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c
> 1: Test timeout computed to be: 1500
> 1:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `initialize': Operation timed out - connect(2) (Errno::ETIMEDOUT)
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `open'
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `wait_port'
> 1: from example_test.rb:73:in `block in '
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:45:in
> `initialize'
> 1: from example_test.rb:70:in `new'
> 1: from example_test.rb:70:in `'
> ^C
> earth:126 rkieley$ ruby -v
> ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1658) [OSX] ruby-example-test test_tools.rb initialize times out and hangs
[
https://issues.apache.org/jira/browse/PROTON-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226842#comment-16226842
]
Roddie Kieley commented on PROTON-1658:
---
[~aconway] good to know re: the port-allocation strategy. A quick test shows
that the updated master no longer times out and hangs on OSX however it also
doesn't run the ruby-example-test or ruby-test-container tests for me on Fedora
25 atm; not sure if that is expected behaviour for the moment.
> [OSX] ruby-example-test test_tools.rb initialize times out and hangs
>
>
> Key: PROTON-1658
> URL: https://issues.apache.org/jira/browse/PROTON-1658
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: ruby-binding
> Environment: OSX 10.11.6, Xcode 7.3.1, ruby 2.0.0p648
>Reporter: Roddie Kieley
>Assignee: Alan Conway
> Fix For: proton-c-0.18.1
>
>
> {code}
> test 1
> Start 1: ruby-example-test
> 1: Test command: /usr/bin/ruby "example_test.rb" "-v"
> 1: Environment variables:
> 1:
> PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/Developer/SDKs/android-sdk-mac_x86-1.6_r1:/Developer/SDKs/android-sdk-mac_x86-1.6_r1/tools:/Developer/SDKs/adt-bundle-mac-x86_64/sdk/tools:/Developer/SDKs/adt-bundle-mac-x86_64/sdk/platform-tools:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c
> 1:
> RUBYLIB=:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/lib:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/spec:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c
> 1: Test timeout computed to be: 1500
> 1:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `initialize': Operation timed out - connect(2) (Errno::ETIMEDOUT)
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `open'
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `wait_port'
> 1: from example_test.rb:73:in `block in '
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:45:in
> `initialize'
> 1: from example_test.rb:70:in `new'
> 1: from example_test.rb:70:in `'
> ^C
> earth:126 rkieley$ ruby -v
> ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1658) [OSX] ruby-example-test test_tools.rb initialize times out and hangs
[
https://issues.apache.org/jira/browse/PROTON-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225990#comment-16225990
]
ASF subversion and git services commented on PROTON-1658:
-
Commit 738c1980eff65051163e53ba2f1a64a0ce2672dd in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=738c198 ]
PROTON-1658: [ruby] simpler, more portable port allocation for tests
The SO_REUSEADDR trick that works on Linux does not work on OSX or Windows.
Use a simpler approach of listen(0), close socket, do real listen. This is
potentially race-prone but works well in practice
The correct solution is to allow the container to listen using a pre-existing
socket,
this is coming with PROTON-1064.
> [OSX] ruby-example-test test_tools.rb initialize times out and hangs
>
>
> Key: PROTON-1658
> URL: https://issues.apache.org/jira/browse/PROTON-1658
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: ruby-binding
> Environment: OSX 10.11.6, Xcode 7.3.1, ruby 2.0.0p648
>Reporter: Roddie Kieley
>Assignee: Alan Conway
> Fix For: proton-c-0.18.1
>
>
> {code}
> test 1
> Start 1: ruby-example-test
> 1: Test command: /usr/bin/ruby "example_test.rb" "-v"
> 1: Environment variables:
> 1:
> PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/Developer/SDKs/android-sdk-mac_x86-1.6_r1:/Developer/SDKs/android-sdk-mac_x86-1.6_r1/tools:/Developer/SDKs/adt-bundle-mac-x86_64/sdk/tools:/Developer/SDKs/adt-bundle-mac-x86_64/sdk/platform-tools:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c
> 1:
> RUBYLIB=:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/lib:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/spec:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c
> 1: Test timeout computed to be: 1500
> 1:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `initialize': Operation timed out - connect(2) (Errno::ETIMEDOUT)
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `open'
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `wait_port'
> 1: from example_test.rb:73:in `block in '
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:45:in
> `initialize'
> 1: from example_test.rb:70:in `new'
> 1: from example_test.rb:70:in `'
> ^C
> earth:126 rkieley$ ruby -v
> ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1658) [OSX] ruby-example-test test_tools.rb initialize times out and hangs
[
https://issues.apache.org/jira/browse/PROTON-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225279#comment-16225279
]
Alan Conway commented on PROTON-1658:
-
The ruby tests are currently using a port-allocation strategy that works on
Linux but not on OSX (or Windows, sigh!), the problem is restricted to the test
harness, it is not a problem with the ruby binding itself when used normally -
i.e. a server listens on a port that is known to be available. I will fix this
ASAP.
The C warning looks like we're missing a declaration or #include file on OSX,
possibly due to a different version of Ruby. If the code is linking then it can
be ignored for now
It will be fixed properly as part of PROTON-1064.
> [OSX] ruby-example-test test_tools.rb initialize times out and hangs
>
>
> Key: PROTON-1658
> URL: https://issues.apache.org/jira/browse/PROTON-1658
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: ruby-binding
> Environment: OSX 10.11.6, Xcode 7.3.1, ruby 2.0.0p648
>Reporter: Roddie Kieley
>Assignee: Alan Conway
>
> {code}
> test 1
> Start 1: ruby-example-test
> 1: Test command: /usr/bin/ruby "example_test.rb" "-v"
> 1: Environment variables:
> 1:
> PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/Developer/SDKs/android-sdk-mac_x86-1.6_r1:/Developer/SDKs/android-sdk-mac_x86-1.6_r1/tools:/Developer/SDKs/adt-bundle-mac-x86_64/sdk/tools:/Developer/SDKs/adt-bundle-mac-x86_64/sdk/platform-tools:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c
> 1:
> RUBYLIB=:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/lib:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/spec:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c
> 1: Test timeout computed to be: 1500
> 1:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `initialize': Operation timed out - connect(2) (Errno::ETIMEDOUT)
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `open'
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `wait_port'
> 1: from example_test.rb:73:in `block in '
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:45:in
> `initialize'
> 1: from example_test.rb:70:in `new'
> 1: from example_test.rb:70:in `'
> ^C
> earth:126 rkieley$ ruby -v
> ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1658) [OSX] ruby-example-test test_tools.rb initialize times out and hangs
[
https://issues.apache.org/jira/browse/PROTON-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16219833#comment-16219833
]
Roddie Kieley commented on PROTON-1658:
---
When building I see the following:
{code}
[ 74%] Swig source
Scanning dependencies of target cproton-ruby
[ 75%] Building C object
proton-c/bindings/ruby/CMakeFiles/cproton-ruby.dir/rubyRUBY_wrap.c.o
/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby/rubyRUBY_wrap.c:2225:12:
warning: implicit declaration of function 'rb_thread_call_without_gvl' is
invalid in C99
[-Wimplicit-function-declaration]
rc = RB_BLOCKING_CALL(pn_messenger_send_no_gvl,
^
/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby/rubyRUBY_wrap.c:2164:26:
note: expanded from macro 'RB_BLOCKING_CALL'
#define RB_BLOCKING_CALL rb_thread_call_without_gvl
^
1 warning generated.
{code}
> [OSX] ruby-example-test test_tools.rb initialize times out and hangs
>
>
> Key: PROTON-1658
> URL: https://issues.apache.org/jira/browse/PROTON-1658
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: ruby-binding
> Environment: OSX 10.11.6, Xcode 7.3.1, ruby 2.0.0p648
>Reporter: Roddie Kieley
>Assignee: Alan Conway
>
> {code}
> test 1
> Start 1: ruby-example-test
> 1: Test command: /usr/bin/ruby "example_test.rb" "-v"
> 1: Environment variables:
> 1:
> PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/Developer/SDKs/android-sdk-mac_x86-1.6_r1:/Developer/SDKs/android-sdk-mac_x86-1.6_r1/tools:/Developer/SDKs/adt-bundle-mac-x86_64/sdk/tools:/Developer/SDKs/adt-bundle-mac-x86_64/sdk/platform-tools:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c
> 1:
> RUBYLIB=:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/lib:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests:/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/spec:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c/bindings/ruby:/Users/rkieley/LocalProjects/issues/PROTON-522/126/proton-c
> 1: Test timeout computed to be: 1500
> 1:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `initialize': Operation timed out - connect(2) (Errno::ETIMEDOUT)
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `open'
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:60:in
> `wait_port'
> 1: from example_test.rb:73:in `block in '
> 1: from
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/ruby/tests/test_tools.rb:45:in
> `initialize'
> 1: from example_test.rb:70:in `new'
> 1: from example_test.rb:70:in `'
> ^C
> earth:126 rkieley$ ruby -v
> ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
