[jira] [Comment Edited] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17254516#comment-17254516
]
Roddie Kieley edited comment on PROTON-2231 at 12/24/20, 12:11 PM:
---
I've now tested in the same way on both an 8 core atom Fedora 32 box as well as
the 6 core macOS box. The behaviour with libuv is broken on both while the
epoll proactor implementation on the Fedora 32 box is well behaved every run.
Looking more closely at libuv we see that the problem behaviours, i.e. stopping
new listening, hanging on exit, or asserting as per the description, appear to
be caused by the fact that at some point in the test execution uv_run does not
return when called in the chain pn_proactor_wait -> leader_lead_lh -> uv_run.
This causes the current leader to not relinquish the lead and the other threads
to be unable to do more work or exit. NOTE that we see this more clearly when
we change the uv_cond_wait call in pn_proactor_wait to un_cond_timedwait for 1
second and observe that the non leader threads dutifully continue to check once
per second rather than blocking while uv_run is blocked and the leader doesn't
change.
Temporarily switching to pn_proactor_get instead of pn_proactor_wait for the
test shows that execution runs successfully until the end when leader_lead_lh
again blocks at uv_run, does not exit, cannot join, and thus the test is still
hung although main test execution behaviour appears correct. If we add a
uv_loop_alive check before the uv_run this check passes, i.e. returns != 0, and
uv_run continues to cause the problem.
As the libuv documentation says that for
[UV_RUN_ONCE|http://docs.libuv.org/en/v1.x/loop.html]
{quote}Note that this function blocks if there are no pending callbacks.
{quote}
Further investigation will be along those lines, however suggestions welcome
[~astitcher] or [~cliffjansen].
was (Author: rkieley):
I've now tested in the same way on both an 8 core atom Fedora 32 box as well as
the 6 core macOS box. The behaviour with libuv is broken on both while the
epoll proactor implementation on the Fedora 32 box is well behaved every run.
Looking more closely at libuv we see that the problem behaviours, i.e. stopping
new listening, hanging on exit, or asserting as per the description, appear to
be caused by the fact that at some point in the test execution uv_run does not
return when called in the chain pn_proactor_wait -> leader_lead_lh -> uv_run.
This causes the current leader to not relinquish the lead and the other threads
to be unable to do more work or exit.
Temporarily switching to pn_proactor_get instead of pn_proactor_wait for the
test shows that execution runs successfully until the end when leader_lead_lh
again blocks at uv_run, does not exit, cannot join, and thus the test is still
hung although main test execution behaviour appears correct. If we add a
uv_loop_alive check before the uv_run this check passes, i.e. returns != 0, and
uv_run continues to cause the problem.
As the libuv documentation says that for
[UV_RUN_ONCE|http://docs.libuv.org/en/v1.x/loop.html]
{quote}Note that this function blocks if there are no pending callbacks.
{quote}
Further investigation will be along those lines, however suggestions welcome
[~astitcher] or [~cliffjansen].
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: freebsd, macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe,
[jira] [Commented] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17254516#comment-17254516
]
Roddie Kieley commented on PROTON-2231:
---
I've now tested in the same way on both an 8 core atom Fedora 32 box as well as
the 6 core macOS box. The behaviour with libuv is broken on both while the
epoll proactor implementation on the Fedora 32 box is well behaved every run.
Looking more closely at libuv we see that the problem behaviours, i.e. stopping
new listening, hanging on exit, or asserting as per the description, appear to
be caused by the fact that at some point in the test execution uv_run does not
return when called in the chain pn_proactor_wait -> leader_lead_lh -> uv_run.
This causes the current leader to not relinquish the lead and the other threads
to be unable to do more work or exit.
Temporarily switching to pn_proactor_get instead of pn_proactor_wait for the
test shows that execution runs successfully until the end when leader_lead_lh
again blocks at uv_run, does not exit, cannot join, and thus the test is still
hung although main test execution behaviour appears correct. If we add a
uv_loop_alive check before the uv_run this check passes, i.e. returns != 0, and
uv_run continues to cause the problem.
As the libuv documentation says that for
[UV_RUN_ONCE|http://docs.libuv.org/en/v1.x/loop.html]
{quote}Note that this function blocks if there are no pending callbacks.
{quote}
Further investigation will be along those lines, however suggestions welcome
[~astitcher] or [~cliffjansen].
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: freebsd, macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241412#comment-17241412
]
Roddie Kieley commented on PROTON-2231:
---
No, I don't think so. It sounds like what we are saying here is the fact that
the code executes an assert like:
{code:java}
static void remove_active_lh(pn_proactor_t *p) {
assert(p->active > 0);
if (--p->active == 0) {
p->need_inactive = true;
}
} {code}
when you attempt to close and remove more listeners than have been opened is
incorrect based on the above. Either that code shouldn't execute at that point
in time or the assert itself is invalid.
I will review the other implementations and the documentation and see about
next steps to address the issue.
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: freebsd, macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17240177#comment-17240177
]
Roddie Kieley commented on PROTON-2231:
---
Assuming that the assert in remove_active_lh is correct and that active
requires being greater than zero then then the problem appears to be that the
threaderciser does not attempt to adhere to that rule. By that I mean that it
will attempt to close more listeners than were opened thus ensuring that the
number of active listeners becomes less than zero.
At the moment I have a partial fix with which it appears in that over the
course of 20 runs we never see it assert during the run but at the moment in
shutting down it can either hang or infrequently assert, which was also
observed in the unmodified code. See my [PROTON-2231
|https://github.com/apache/qpid-proton/compare/master...RoddieKieley:PROTON-2231]
branch, commit
[49efdd5c17d6f5f0b83ec9820da54841df18145d|https://github.com/RoddieKieley/qpid-proton/commit/49efdd5c17d6f5f0b83ec9820da54841df18145d]
in particular. Needs a bit more work but appears to be on the right track.
Here's snippet from a failed run:
{code}
.
.
.
(7556e000) [0x7f971b80de00] close-listen
(755f1000) [0x7f971b80de00] PN_LISTEN_CLOSE on :::53389, opened: 0
(7505) [0x7f9719200100] wake
(7525c000) [0x7f9718500330] connect
(75468000) [0x7f9718600c20] wake
(75156000) [0x7f971b80d800] listen
(75156000) [0x7f9719100850] wake
(755f1000) [0x7f971b80d800] PN_LISTEN_OPEN on :::53396, opened: 1
(75362000) [0x7f971b801600] listen
(750d3000) [0x7f971b801600] PN_LISTEN_OPEN on :::53397, opened: 2
(75468000) [0x7f971b80ea00] listen
(753e5000) [0x7f971b80ea00] PN_LISTEN_OPEN on :::53398, opened: 3
(75362000) [0x7f97184036c0] wake
(7556e000) [0x7f9718600570] wake
(7556e000) [0x7f9718600c20] wake
(75468000) [0x7f971b801600] close-listen
(752df000) [0x7f971b801600] PN_LISTEN_CLOSE on :::53397, opened: 2
(75156000) [0x7f9719200100] wake
(7505) [0x7f9719100850] wake
(7525c000) [0x7f9718809800] listen
(7525c000) [0x7f9718500330] wake
(754eb000) [0x7f9718809800] PN_LISTEN_OPEN on :::53399, opened: 3
(7525c000) [0x7f9719200100] wake
(7556e000) [0x7f971c007e00] close-listen
(754eb000) [0x7f971c007e00] PN_LISTEN_CLOSE on :::53371, opened: 2
(75362000) [0x7f9718404a70] connect
(75362000) [0x7f97184036c0] wake
(75468000) [0x7f9718602830] connect
(75468000) [0x7f971b805600] listen
(750d3000) [0x7f971b805600] PN_LISTEN_OPEN on :::53402, opened: 3
(750d3000) [0x7f9718600e30] connect
(10d6625c0) shut down
(75156000) user_thread end
(7525c000) user_thread end
(7505) user_thread end
(75362000) user_thread end
(7556e000) user_thread end
(75468000) user_thread end
(10d6625c0) disconnect
(755f1000) [0x7f971b805600] PN_LISTEN_CLOSE on :::53402, opened: 2
(751d9000) [0x7f971b80ea00] PN_LISTEN_CLOSE on :::53398, opened: 1
(755f1000) [0x7f971c000600] PN_LISTEN_CLOSE on :::53392, opened: 0
(753e5000) [0x7f971b80d800] PN_LISTEN_CLOSE on :::53396, opened: -3
(750d3000) [0x7f9718809800] PN_LISTEN_CLOSE on :::53399, opened: -1
(752df000) [0x7f971b008c00] PN_LISTEN_CLOSE on :::53391, opened: -2
Assertion failed: (p->active > 0), function remove_active_lh, file
/wip/src/github.com/apache/qpid-proton/c/src/proactor/libuv.c, line 394.
{code}
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: freebsd, macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian
[jira] [Commented] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239854#comment-17239854
]
Roddie Kieley commented on PROTON-2231:
---
I think everything I've seen indicates that it is not platform specific.
Tracing through the function calls with the timeouts disabled we see that it
always the code path always comes directly through remove_active which
eventually asserts that active must be greater than zero for you to call a
remove that will decrement it. As far as I can tell the threadercizer does not
track open versus closed listeners and can close more than have been opened,
although at this point this is from recollection.
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: freebsd, macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227570#comment-17227570
]
Roddie Kieley commented on PROTON-2231:
---
After collecting lots of logging using the -debug method via:
{code}
./c-threaderciser -time 10 -threads 12 -debug -no-timeout -no-cancel-timeout
{code}
A very short reproduction of the assertion was recorded:
{code}
i7mbp:tests rkieley$ ./c-threaderciser -time 10 -threads 12 -debug -no-timeout
-no-cancel-timeout 2>&1 >>
/wip/issues/issues.apache.org/PROTON-2231/threader-110620-4-no-timeouts-1.out |
tee
/wip/issues/issues.apache.org/PROTON-2231/threader-110620-4-no-timeouts-1.out
(1053a35c0) [0x7fb3c8802800] listen
(709b) user_thread start
(70a33000) proactor_thread start
(70ab6000) user_thread start
(70b39000) proactor_thread start
(70c3f000) proactor_thread start
(709b) [0x7fb3c7d006a0] connect
(70cc2000) user_thread start
(70bbc000) user_thread start
(70d45000) proactor_thread start
(70dc8000) user_thread start
(70bbc000) [0x7fb3c9100070] connect
(70e4b000) proactor_thread start
(70ece000) user_thread start
(70f51000) proactor_thread start
(709b) [0x7fb3c8802800] close-listen
(709b) [0x7fb3c9100070] wake
(70dc8000) [0x7fb3c7d01f10] connect
(70dc8000) [0x7fb3c980d200] listen
(70dc8000) [0x7fb3c8802800] close-listen
(70dc8000) [0x7fb3c9100070] wake
(70ece000) [0x7fb3c7f02eb0] connect
(709b) [0x7fb3c980de00] listen
(70bbc000) [0x7fb3c7d006a0] wake
(70ece000) [0x7fb3c980d200] close-listen
(70cc2000) [0x7fb3c7d006a0] wake
(70bbc000) [0x7fb3c7f041f0] connect
(70bbc000) [0x7fb3c7f02eb0] wake
(70ece000) [0x7fb3c9100070] wake
(70a33000) [0x7fb3c8802800] listening on :::62859
(70a33000) [0x7fb3c7c04e60] connect
(70c3f000) [0x7fb3c980de00] listening on :::62860
(70c3f000) [0x7fb3c9101200] connect
(70dc8000) [0x7fb3c7f02c90] connect
(70dc8000) [0x7fb3c7f02c90] wake
(709b) [0x7fb3c7f02c90] wake
(70bbc000) [0x7fb3c980de00] close-listen
Assertion failed: (p->active > 0), function remove_active_lh, file
/wip/src/github.com/apache/qpid-proton/c/src/proactor/libuv.c, line 394.
i7mbp:tests rkieley$
{code}
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227457#comment-17227457
]
Roddie Kieley commented on PROTON-2231:
---
Investigation ongoing. Seeing two variations of the hang at the end of the
threaderciser using the following on a 6 core i7 based mac:
{code}
for i in {1..10}; do `echo echo $i; date +%H:%M:%S; ./c-threaderciser -time 10
-threads 12`; done;
{code}
This hangs the very first time it runs in many cases in one of two places
{code}
for (i = 0; i < threads/2; ++i) pthread_join(proactor_threads[i], );
{code}
with 6 of the 7 threads sitting in pn_proactor_wait
OR threaderciser hangs at
{code}
global_destroy()
{code}
which itself is hung on
{code}
pn_proactor_free(g->proactor);
{code}
As well I also see the Assertion failed from the above comment periodically.
More investigation and understanding required to put the pieces together.
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17215708#comment-17215708
]
Roddie Kieley commented on PROTON-2231:
---
While I have not yet attempted to reproduce using libuv on other platforms,
either Linux or Windows, I can now confirm local reproduction on macOS 10.14
using today's latest code:
{code}
i7mbp:1 rkieley$ ctest -VV -R c-threaderciser --timeout 60
UpdateCTestConfiguration from
:/wip/builds/github.com/apache/qpid-proton/101620/1/DartConfiguration.tcl
Parse Config
file:/wip/builds/github.com/apache/qpid-proton/101620/1/DartConfiguration.tcl
UpdateCTestConfiguration from
:/wip/builds/github.com/apache/qpid-proton/101620/1/DartConfiguration.tcl
Parse Config
file:/wip/builds/github.com/apache/qpid-proton/101620/1/DartConfiguration.tcl
Test project /wip/builds/github.com/apache/qpid-proton/101620/1
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 6
Start 6: c-threaderciser
6: Test command: /opt/local/bin/python
"/wip/src/github.com/apache/qpid-proton/scripts/env.py" "--"
"/wip/builds/github.com/apache/qpid-proton/101620/1/c/tests/c-threaderciser"
6: Test timeout computed to be: 60
6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
connect, close-connect, wake, timeout, cancel-timeout]
6: Assertion failed: (p->active > 0), function remove_active_lh, file
/wip/src/github.com/apache/qpid-proton/c/src/proactor/libuv.c, line 394.
1/1 Test #6: c-threaderciser ..***Failed1.16 sec
0% tests passed, 1 tests failed out of 1
Total Test time (real) = 1.17 sec
The following tests FAILED:
6 - c-threaderciser (Failed)
Errors while running CTest
i7mbp:1 rkieley$
{code}
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley reassigned PROTON-2231:
-
Assignee: Roddie Kieley
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2213) [ruby] Consistent failure in ContainerTest#test_stop
Roddie Kieley created PROTON-2213:
-
Summary: [ruby] Consistent failure in ContainerTest#test_stop
Key: PROTON-2213
URL: https://issues.apache.org/jira/browse/PROTON-2213
Project: Qpid Proton
Issue Type: Bug
Components: ruby-binding
Affects Versions: proton-c-0.30.0, proton-c-0.31.0
Environment: OSX 10.11.6
Ruby 2.0.0-648
Reporter: Roddie Kieley
Assignee: Alan Conway
Observed on osx 10.11.6, ruby 2.0.0-648, on a dual core machine:
{code:java}
test 23
Start 23: ruby-test-container23: Test command: /opt/local/bin/python
.
.
.
23: Test timeout computed to be: 1500
23: Run options: -v --seed 61751
23:
23: # Running:
23:
.
.
.
23: ContainerTest#test_stop = 1.01 s = F
.
.
.
23: 1) Failure:
23: ContainerTest#test_stop [/.../qpid-proton/ruby/tests/test_container.rb:150]:
23: Expected nil to be truthy.
23:
23: 22 runs, 111 assertions, 1 failures, 0 errors, 0 skips
1/2 Test #23: ruby-test-container ..***Failed2.46 sec {code}
test_container.rb:150
{code:ruby}
threads.each { |t| assert t.join(1) }
{code}
Warrants further investigation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2174) [go] go-test TestHeartbeat fails with latest macOS image
[
https://issues.apache.org/jira/browse/PROTON-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley resolved PROTON-2174.
---
Fix Version/s: proton-c-0.31.0
Resolution: Fixed
As per the noted commits I added 1000ms to the TestHeartbeat test as it
appeared that the previously given timeout of 400ms was too short for the
travis vm to execute successfully. Also needed to implement a "workaround" by
doing a brew update due to a brew bundle issue caused by a recent change on the
brew distribution side - see .travis.yml for the update and the link.
> [go] go-test TestHeartbeat fails with latest macOS image
>
>
> Key: PROTON-2174
> URL: https://issues.apache.org/jira/browse/PROTON-2174
> Project: Qpid Proton
> Issue Type: Test
> Components: go-binding
>Reporter: Roddie Kieley
>Assignee: Roddie Kieley
>Priority: Major
> Fix For: proton-c-0.31.0
>
>
> After a recent update to pick up the latest macOS image, now using Xcode
> 11.3, we see a new failure during this [travis-ci
> run|https://travis-ci.org/apache/qpid-proton/jobs/641271619].
> {quote}
> 26: === RUN TestHeartbeat
> 26: --- FAIL: TestHeartbeat (0.45s)
> 26: electron_test.go:325: connection failed to time out
> {quote}
> This looks virtually the same as failures seen prior to the move to go
> modules as discussed in this PROTON-2105
> [comment|https://issues.apache.org/jira/browse/PROTON-2105?focusedCommentId=16962578=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16962578]
> Testing locally on macOS 10.14 with Xcode 10.2 shows no TestHeartbeat
> failures over 100 continuous attempts. Further investigation required.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2174) [go] go-test TestHeartbeat fails with latest macOS image
Roddie Kieley created PROTON-2174:
-
Summary: [go] go-test TestHeartbeat fails with latest macOS image
Key: PROTON-2174
URL: https://issues.apache.org/jira/browse/PROTON-2174
Project: Qpid Proton
Issue Type: Test
Components: go-binding
Reporter: Roddie Kieley
Assignee: Roddie Kieley
After a recent update to pick up the latest macOS image, now using Xcode 11.3,
we see a new failure during this [travis-ci
run|https://travis-ci.org/apache/qpid-proton/jobs/641271619].
{quote}
26: === RUN TestHeartbeat
26: --- FAIL: TestHeartbeat (0.45s)
26: electron_test.go:325: connection failed to time out
{quote}
This looks virtually the same as failures seen prior to the move to go modules
as discussed in this PROTON-2105
[comment|https://issues.apache.org/jira/browse/PROTON-2105?focusedCommentId=16962578=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16962578]
Testing locally on macOS 10.14 with Xcode 10.2 shows no TestHeartbeat failures
over 100 continuous attempts. Further investigation required.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2160) [go] Builds run and fail with Golang < 1.11
Roddie Kieley created PROTON-2160: - Summary: [go] Builds run and fail with Golang < 1.11 Key: PROTON-2160 URL: https://issues.apache.org/jira/browse/PROTON-2160 Project: Qpid Proton Issue Type: Bug Components: go-binding Environment: Apache Jenkins - Ubuntu go 1.10 Reporter: Roddie Kieley Assignee: Roddie Kieley After the changes for PROTON-2105 to add go module support a number of ubuntu based Jenkins builds started failing. Taking a look at the [log|https://builds.apache.org/job/Qpid-proton-c/2051/console] we see that the go version is less than the version where Golang introduced modules, 1.11. A check should be introduced so that these builds will not be attempted when it is found that the Golang version is less than that required. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2107) Go module support
[ https://issues.apache.org/jira/browse/PROTON-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16962582#comment-16962582 ] Roddie Kieley commented on PROTON-2107: --- [~thitiphong.a] I've just committed work via PROTON-2105 to implement support for go modules. Please give it a try and let us know if it resolves your issue. NOTE that the module is github.com/apache/qpid-proton as per [go.mod|https://github.com/apache/qpid-proton/blob/master/go.mod] and that go 1.11 is now required. > Go module support > - > > Key: PROTON-2107 > URL: https://issues.apache.org/jira/browse/PROTON-2107 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Affects Versions: proton-c-0.29.0 >Reporter: Thtiphong Anansukkasem >Assignee: Roddie Kieley >Priority: Major > > I found the error , when i run "go get" command in go module enabled project > $go get -v qpid.apache.org/electron > go: finding qpid.apache.org latest > go get qpid.apache.org/electron: module qpid.apache.org@upgrade > (v0.0.0-20190919033840-551513f49822) found, but does not contain package > qpid.apache.org/electron > $ go get -v qpid.apache.org/amqp > go: finding qpid.apache.org latest > go get qpid.apache.org/amqp: module qpid.apache.org@upgrade > (v0.0.0-20190919033840-551513f49822) found, but does not contain package > qpid.apache.org/amqp > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2105) Support Go modules
[ https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roddie Kieley resolved PROTON-2105. --- Fix Version/s: proton-c-0.30.0 Resolution: Implemented > Support Go modules > -- > > Key: PROTON-2105 > URL: https://issues.apache.org/jira/browse/PROTON-2105 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Ulf Lilleengen >Assignee: Roddie Kieley >Priority: Major > Fix For: proton-c-0.30.0 > > > As of Go 1.12, go module support is available. In order to manage > dependencies using go modules, dependencies must also be using go modules. > Therefore, adding a go.mod file to each module would allow qpid proton go > bindings to be managed as a go module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2105) Support Go modules
[
https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16962578#comment-16962578
]
Roddie Kieley commented on PROTON-2105:
---
As above I committed the work for the go module support. Locally all tests
pass, however I do note that in travis in the build *before* these commits,
2205, the [Xcode 10.1
variant|https://travis-ci.org/apache/qpid-proton/jobs/603007629] shows the
electron go-test TestHeartbeat failing:
{code}
26: === RUN TestHeartbeat
362126: --- FAIL: TestHeartbeat (0.49s)
362226: electron_test.go:325: connection failed to time out
{code}
The commits did not change the state with the tests still only failing for the
subsequent 2206 build job in the [Xcode 10.1
variant|https://travis-ci.org/apache/qpid-proton/jobs/604743078] for the same
reason:
{code}
26: === RUN TestHeartbeat
363926: --- FAIL: TestHeartbeat (0.41s)
364026: electron_test.go:325: connection failed to time out
{code}
As this appears unrelated to the committed work I will mark this complete.
> Support Go modules
> --
>
> Key: PROTON-2105
> URL: https://issues.apache.org/jira/browse/PROTON-2105
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
>Reporter: Ulf Lilleengen
>Assignee: Roddie Kieley
>Priority: Major
>
> As of Go 1.12, go module support is available. In order to manage
> dependencies using go modules, dependencies must also be using go modules.
> Therefore, adding a go.mod file to each module would allow qpid proton go
> bindings to be managed as a go module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (DISPATCH-1384) Fix tests in Travis CI on macOS
[
https://issues.apache.org/jira/browse/DISPATCH-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956518#comment-16956518
]
Roddie Kieley edited comment on DISPATCH-1384 at 10/21/19 11:23 PM:
[~jdanek] In taking a look at isprint I realized that the real change here is
that you are letting sprintf handle the non 7-bit [ASCII
values|http://www.asciitable.com] with the c < 128 change. Those would likely
be impacted by encoding and locale, although I'm not 100% sure that's relevant
other than the fact that via sprintf a format is provided rather than trying to
shoehorn the value directly into a char array.
While there is likely a more elegant way of handling the situation, this may be
enough for now. I'll see about getting a chance to take a closer look.
was (Author: rkieley):
[~jdanek] In taking a look at isprint I realized that the real change here is
that you are letting sprint handle the non 7-bit [ASCII
values|http://www.asciitable.com] with the c < 128 change. Those would likely
be impacted by encoding and locale, although I'm not 100% sure that's relevant
other than the fact that via sprintf a format is provided rather than trying to
shoehorn the value directly into a char array.
While there is likely a more elegant way of handling the situation, this may be
enough for now. I'll see about getting a chance to take a closer look.
> Fix tests in Travis CI on macOS
> ---
>
> Key: DISPATCH-1384
> URL: https://issues.apache.org/jira/browse/DISPATCH-1384
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Reporter: Jiri Daněk
>Assignee: Jiri Daněk
>Priority: Major
> Labels: macOS
>
> {noformat}
> The following tests FAILED:
> 9 - unit_tests (SEGFAULT)
>23 - system_tests_policy (Timeout)
>28 - system_tests_sasl_plain (Failed)
>38 - system_tests_auth_service_plugin (Failed)
>39 - system_tests_authz_service_plugin (Failed)
>48 - system_tests_bad_configuration (Failed)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1384) Fix tests in Travis CI on macOS
[
https://issues.apache.org/jira/browse/DISPATCH-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956518#comment-16956518
]
Roddie Kieley commented on DISPATCH-1384:
-
[~jdanek] In taking a look at isprint I realized that the real change here is
that you are letting sprint handle the non 7-bit [ASCII
values|http://www.asciitable.com] with the c < 128 change. Those would likely
be impacted by encoding and locale, although I'm not 100% sure that's relevant
other than the fact that via sprintf a format is provided rather than trying to
shoehorn the value directly into a char array.
While there is likely a more elegant way of handling the situation, this may be
enough for now. I'll see about getting a chance to take a closer look.
> Fix tests in Travis CI on macOS
> ---
>
> Key: DISPATCH-1384
> URL: https://issues.apache.org/jira/browse/DISPATCH-1384
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Reporter: Jiri Daněk
>Assignee: Jiri Daněk
>Priority: Major
> Labels: macOS
>
> {noformat}
> The following tests FAILED:
> 9 - unit_tests (SEGFAULT)
>23 - system_tests_policy (Timeout)
>28 - system_tests_sasl_plain (Failed)
>38 - system_tests_auth_service_plugin (Failed)
>39 - system_tests_authz_service_plugin (Failed)
>48 - system_tests_bad_configuration (Failed)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2122) Hardcoded limit of 16 sasl mechanisms is insufficient on macOS
[
https://issues.apache.org/jira/browse/PROTON-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955707#comment-16955707
]
Roddie Kieley commented on PROTON-2122:
---
[~jdanek] Hadn't seen this comment but realized same here in testing. I also
changed the [magic
16|https://github.com/apache/qpid-proton/blob/0.29.0/c/src/sasl/sasl.c#L475] to
be a magic 32 here as on this version of macOS, 10.14, it was listing 24 values
for 12 in duplicate:
{quote}
SRP SRP GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 SCRAM-SHA-256 SCRAM-SHA-1
GS2-KRB5 GS2-IAKERB GSS-SPNEGO GSSAPI GSS-SPNEGO GSSAPI DIGEST-MD5 DIGEST-MD5
OTP OTP NTLM CRAM-MD5 NTLM CRAM-MD5 ANONYMOUS ANONYMOUS
{quote}
With the magic 32 sasl related tests pass and close the gap in earlier reported
test success rate:
{quote}
62/62 Test #62: system_tests_router_mesh .. Passed
37.57 sec
82% tests passed, 11 tests failed out of 62
Total Test time (real) = 945.43 sec
The following tests FAILED:
26 - system_tests_protocol_settings (Failed)
27 - system_tests_qdmanage (Failed)
29 - system_tests_sasl_plain (Failed)
37 - system_tests_log_message_components (Failed)
39 - system_tests_auth_service_plugin (Failed)
40 - system_tests_authz_service_plugin (Failed)
43 - system_tests_topology_disposition (Failed)
50 - system_tests_ssl (Failed)
54 - system_tests_http (Failed)
57 - system_tests_core_client (Failed)
60 - system_tests_multicast (Failed)
Errors while running CTest
(p3venv) i7mbp:0 rkieley$
{quote}
As to 1), why there are duplicates, I'm not sure. I don't recall it being this
way when I did the original OSX work via PROTON-522, although I'd have to look
at my logs to be sure. At the moment I'm on 10.14 with cyrus-sasl 2.1.27 vs.
10.11 with cyrus-sasl 2.1.26, so it's possible either of those could make a
difference. Would need to test to find out. In neither case was there a mixture
of system sasl and MacPorts sasl as that had caused other subtle issues that
were resolved by ensuring only one or the other was utilized. Maybe
[~astitcher] knows off hand.
For 2), I always got a message here, 'Abort Trap: 6'. Stepping through with the
debugger would always yield a SIGABRT. Taking a look at what abort trap 6
indicates, it says that you've done some bad memory stuff and if you step
through with the debugger the failure occurs
[here|https://github.com/apache/qpid-proton/blob/0.29.0/c/src/sasl/sasl.c#L484]
calling {code}
free(mechlist)
{code}
Ultimately the solution here is to not have a magic number and be a little more
sophisticated in handling the memory. However I think the can could be kicked
down the road a little further by going with the magic 32 for the moment, and
updating the TODO to say something like
{quote}
// TODO: PROTON-2122: Replace magic number with dynamically sized memory
{quote}
which would at least eliminate the failures for the moment and allow the test
failures to be cleaned up to 100% hopefully.
> Hardcoded limit of 16 sasl mechanisms is insufficient on macOS
> --
>
> Key: PROTON-2122
> URL: https://issues.apache.org/jira/browse/PROTON-2122
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.29.0
> Environment: macOS 10.14
>Reporter: Jiri Daněk
>Priority: Major
>
> On macOS, any time a SASL exchange happens in tests, e.g.
> {{cpp-example-container}} or qpid dispatch tests, or when
> {{cpp/examples/simple_send}} connects to {{cpp/examples/broker}}, the broker
> crashes with the following stack trace
> {noformat}
> Thread 1 Crashed:
> 0 libsystem_kernel.dylib 0x7fff697c62c6 __pthread_kill + 10
> 1 libsystem_pthread.dylib 0x7fff69881bf1 pthread_kill + 284
> 2 libsystem_c.dylib 0x7fff69730745 __abort + 144
> 3 libsystem_c.dylib 0x7fff69730ff3 __stack_chk_fail +
> 205
> 4 libqpid-proton-core.10.dylib0x000106d81f89
> pni_post_sasl_frame + 1321
> 5 ??? 0x7fd57acb59bb 0 + 140554864908731
> {noformat}
> AddressSanitizer (Valgrind does not run on most recent macOS releases) points
> out the reason.
> {noformat}
> $ ../cmake-build-debug/cpp/examples/broker
> broker listening on 5672
> =
> ==42793==ERROR: AddressSanitizer: stack-buffer-overflow on address
> 0x7c4bcbe0 at pc 0x0001013663e1 bp 0x7c4bc830 sp 0x7c4bc828
> WRITE of size 8 at 0x7c4bcbe0 thread T3
> #0 0x1013663e0 in pni_split_mechs sasl.c:443
> #1 0x1013646ea in pni_post_sasl_frame sasl.c:480
> #2 0x101357fad in pn_output_write_sasl
[jira] [Commented] (DISPATCH-1384) Fix tests in Travis CI on macOS
[
https://issues.apache.org/jira/browse/DISPATCH-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953339#comment-16953339
]
Roddie Kieley commented on DISPATCH-1384:
-
[~jdanek] I'm seeing 67% pass on master here and 69% with your jd_macos_tests
branch. Some % lost due to no saslpasswd2 executable being found, not sure how
much of the rest of the discrepancy is local environment at this point:
master
{code}
67% tests passed, 20 tests failed out of 61
Total Test time (real) = 987.86 sec
The following tests FAILED:
9 - unit_tests (SEGFAULT)
14 - system_tests_link_routes (Child aborted)
21 - system_tests_handle_failover (Failed)
24 - system_tests_policy (Child aborted)
26 - system_tests_protocol_settings (Failed)
27 - system_tests_qdmanage (Failed)
28 - system_tests_qdstat (Failed)
29 - system_tests_sasl_plain (Failed)
30 - system_tests_user_id (Failed)
31 - system_tests_user_id_proxy (Failed)
37 - system_tests_log_message_components (Failed)
39 - system_tests_auth_service_plugin (Failed)
40 - system_tests_authz_service_plugin (Failed)
43 - system_tests_topology_disposition (Failed)
49 - system_tests_bad_configuration (Failed)
50 - system_tests_ssl (Failed)
54 - system_tests_http (Failed)
56 - system_tests_core_client (Failed)
57 - system_tests_address_lookup (Child aborted)
59 - system_tests_multicast (Failed)
Errors while running CTest
{code}
jd_macos_tests
{code}
69% tests passed, 18 tests failed out of 59
Total Test time (real) = 892.27 sec
The following tests FAILED:
9 - unit_tests (SEGFAULT)
13 - system_tests_link_routes (Child aborted)
20 - system_tests_handle_failover (Failed)
23 - system_tests_policy (Child aborted)
25 - system_tests_protocol_settings (Failed)
26 - system_tests_qdmanage (Failed)
27 - system_tests_qdstat (Failed)
28 - system_tests_sasl_plain (Failed)
29 - system_tests_user_id (Failed)
30 - system_tests_user_id_proxy (Failed)
36 - system_tests_log_message_components (Failed)
38 - system_tests_auth_service_plugin (Failed)
39 - system_tests_authz_service_plugin (Failed)
42 - system_tests_topology_disposition (Failed)
49 - system_tests_ssl (Failed)
52 - system_tests_http (Failed)
55 - system_tests_core_client (Failed)
56 - system_tests_address_lookup (Child aborted)
{code}
I also noted that python crashes multiple times during the run. Outside of the
steps from the travis yaml is there any further specific configuration
expected, or exact versions needed to get the higher pass rate do you know?
> Fix tests in Travis CI on macOS
> ---
>
> Key: DISPATCH-1384
> URL: https://issues.apache.org/jira/browse/DISPATCH-1384
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Reporter: Jiri Daněk
>Assignee: Jiri Daněk
>Priority: Major
>
> {noformat}
> The following tests FAILED:
> 9 - unit_tests (SEGFAULT)
>23 - system_tests_policy (Timeout)
>28 - system_tests_sasl_plain (Failed)
>38 - system_tests_auth_service_plugin (Failed)
>39 - system_tests_authz_service_plugin (Failed)
>48 - system_tests_bad_configuration (Failed)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-2105) Support Go modules
[ https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950655#comment-16950655 ] Roddie Kieley edited comment on PROTON-2105 at 10/14/19 1:40 AM: - [~lulf],[~aconway] Had thought I would need to do something with the GO111MODULE env var but it turns out that in Travis CI the matrix'd linux build and the Xcode10.1 macOS image were failing simply because they had go 1.11 and NOT 1.12 as the require statement specified in the go.mod file. The Xcode 8.3 build was failing as it is configured with go 1.9. I relaxed the go.mod require version to 1.11 and updated the .travis.yml to explicitly set it to build for the macOS Xcode10.1 image and to NOT build for the macOS Xcode8.3 based image. This resulted in a passing travis ci via [build #2183https://www.travis-ci.org/apache/qpid-proton/builds/597417689] Not sure what else needs to be done here as it should build and the tests should run successfully in most cases now assuming the require version is met. Thoughts? was (Author: rkieley): [~lulf][~aconway] Had thought I would need to do something with the GO111MODULE env var but it turns out that in Travis CI the matrix'd linux build and the Xcode10.1 macOS image were failing simply because they had go 1.11 and NOT 1.12 as the require statement specified in the go.mod file. The Xcode 8.3 build was failing as it is configured with go 1.9. I relaxed the go.mod require version to 1.11 and updated the .travis.yml to explicitly set it to build for the macOS Xcode10.1 image and to NOT build for the macOS Xcode8.3 based image. This resulted in a passing travis ci via [build #2183https://www.travis-ci.org/apache/qpid-proton/builds/597417689] Not sure what else needs to be done here as it should build and the tests should run successfully in most cases now assuming the require version is met. Thoughts? > Support Go modules > -- > > Key: PROTON-2105 > URL: https://issues.apache.org/jira/browse/PROTON-2105 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Ulf Lilleengen >Assignee: Roddie Kieley >Priority: Major > > As of Go 1.12, go module support is available. In order to manage > dependencies using go modules, dependencies must also be using go modules. > Therefore, adding a go.mod file to each module would allow qpid proton go > bindings to be managed as a go module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2105) Support Go modules
[ https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950655#comment-16950655 ] Roddie Kieley commented on PROTON-2105: --- [~lulf][~aconway] Had thought I would need to do something with the GO111MODULE env var but it turns out that in Travis CI the matrix'd linux build and the Xcode10.1 macOS image were failing simply because they had go 1.11 and NOT 1.12 as the require statement specified in the go.mod file. The Xcode 8.3 build was failing as it is configured with go 1.9. I relaxed the go.mod require version to 1.11 and updated the .travis.yml to explicitly set it to build for the macOS Xcode10.1 image and to NOT build for the macOS Xcode8.3 based image. This resulted in a passing travis ci via [build #2183https://www.travis-ci.org/apache/qpid-proton/builds/597417689] Not sure what else needs to be done here as it should build and the tests should run successfully in most cases now assuming the require version is met. Thoughts? > Support Go modules > -- > > Key: PROTON-2105 > URL: https://issues.apache.org/jira/browse/PROTON-2105 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Ulf Lilleengen >Assignee: Roddie Kieley >Priority: Major > > As of Go 1.12, go module support is available. In order to manage > dependencies using go modules, dependencies must also be using go modules. > Therefore, adding a go.mod file to each module would allow qpid proton go > bindings to be managed as a go module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-2105) Support Go modules
[ https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16948128#comment-16948128 ] Roddie Kieley edited comment on PROTON-2105 at 10/10/19 2:14 AM: - [~lulf] [~aconway] Looks like the [travis build|https://www.travis-ci.org/apache/qpid-proton/builds/595899023] is flagging that it doesn't have go 1.12 in a couple of cases and didn't build quite right in one other case - will investigate when possible. was (Author: rkieley): [~lulf] [~aconway] Looks like travis is flagging that it doesn't have go 1.12 in a couple of cases and didn't build quite right in one other case - will investigate when possible. > Support Go modules > -- > > Key: PROTON-2105 > URL: https://issues.apache.org/jira/browse/PROTON-2105 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Ulf Lilleengen >Assignee: Roddie Kieley >Priority: Major > > As of Go 1.12, go module support is available. In order to manage > dependencies using go modules, dependencies must also be using go modules. > Therefore, adding a go.mod file to each module would allow qpid proton go > bindings to be managed as a go module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2105) Support Go modules
[ https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16948128#comment-16948128 ] Roddie Kieley commented on PROTON-2105: --- [~lulf] [~aconway] Looks like travis is flagging that it doesn't have go 1.12 in a couple of cases and didn't build quite right in one other case - will investigate when possible. > Support Go modules > -- > > Key: PROTON-2105 > URL: https://issues.apache.org/jira/browse/PROTON-2105 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Ulf Lilleengen >Assignee: Roddie Kieley >Priority: Major > > As of Go 1.12, go module support is available. In order to manage > dependencies using go modules, dependencies must also be using go modules. > Therefore, adding a go.mod file to each module would allow qpid proton go > bindings to be managed as a go module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2105) Support Go modules
[
https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16948126#comment-16948126
]
Roddie Kieley commented on PROTON-2105:
---
[~lulf] [~aconway] I've added a branch in the GitHub Apache Qpid Proton repo,
[PROTON-2105-apache|https://github.com/apache/qpid-proton/tree/PROTON-2105-apache],
which contains an updated go tree with a go.mod plus other required changes to
source and markdown files. This removes the qpid.apache.org import magic in
favour of the absolute and currently favoured with modules
"github.com/apache/qpid-proton" module naming and package import references
that look like "github.com/apache/qpid-proton/go/pkg/amqp" etc.
I've added a most basic GoLand project using this branch via a go.mod reference
in my GitHub repo under
[PROTON-2105-apache-project|https://github.com/RoddieKieley/PROTON-2105-apache-project]
where the key piece is the
[go.mod|https://github.com/RoddieKieley/PROTON-2105-apache-project/blob/master/go.mod]
file which, after automatic GoLand processing looks like:
{code:java}
module PROTON-2105-apache-project
go 1.12
require github.com/apache/qpid-proton v0.0.0-20191010013420-0c20a4dfd1f7{code}
but started out like
{code:java}
module PROTON-2105-apache-project
go 1.12
require github.com/apache/qpid-proton PROTON-2105-apache{code}
to reference the branch.
In
[main.go|https://github.com/RoddieKieley/PROTON-2105-apache-project/blob/master/main.go]
I reference the amqp package via:
{code:java}
"github.com/apache/qpid-proton/go/pkg/amqp" {code}
Please give the
[PROTON-2105-apache|https://github.com/apache/qpid-proton/tree/PROTON-2105-apache]
branch a try when you get a chance and let me know if it works for you and
anything you see that needs to be completed/changed/etc.
> Support Go modules
> --
>
> Key: PROTON-2105
> URL: https://issues.apache.org/jira/browse/PROTON-2105
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
>Reporter: Ulf Lilleengen
>Assignee: Roddie Kieley
>Priority: Major
>
> As of Go 1.12, go module support is available. In order to manage
> dependencies using go modules, dependencies must also be using go modules.
> Therefore, adding a go.mod file to each module would allow qpid proton go
> bindings to be managed as a go module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2105) Support Go modules
[ https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16943261#comment-16943261 ] Roddie Kieley commented on PROTON-2105: --- Thanks for the details and direction [~aconway]! Perhaps I should have read the readme sooner as I had completely forgotten any of the details I had previously known about the magic branch. Will proceed to prepare the re-organization and go 1.12 based go.mod file as above along with any build related changes as required. > Support Go modules > -- > > Key: PROTON-2105 > URL: https://issues.apache.org/jira/browse/PROTON-2105 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Ulf Lilleengen >Assignee: Roddie Kieley >Priority: Major > > As of Go 1.12, go module support is available. In order to manage > dependencies using go modules, dependencies must also be using go modules. > Therefore, adding a go.mod file to each module would allow qpid proton go > bindings to be managed as a go module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2105) Support Go modules
[
https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942432#comment-16942432
]
Roddie Kieley commented on PROTON-2105:
---
[~lulf] After reading the docs and looking at some examples I'm not sure we'll
be able to avoid something similar to the above. As per [Using Go
Modules|https://blog.golang.org/using-go-modules]:
{quote}
The go.mod file defines the module’s module path, which is also the import path
used for the root directory...
{quote}
So it appears in the qpid-proton go.mod file we'd have something like
{noformat}
module github.com/apache/qpid-proton
{noformat}
and in the import to get from the root to the go source for a package we need
the above + go/src/qpid.apache.org/amqp
{noformat}
import "github.com/apache/qpid-proton/go/src/qpid.apache.org/amqp"
{noformat}
And as well we don't get to require qpid-proton-c from the go side which would
be more accurate given that it depends on the native c libraries produced.
> Support Go modules
> --
>
> Key: PROTON-2105
> URL: https://issues.apache.org/jira/browse/PROTON-2105
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
>Reporter: Ulf Lilleengen
>Assignee: Roddie Kieley
>Priority: Major
>
> As of Go 1.12, go module support is available. In order to manage
> dependencies using go modules, dependencies must also be using go modules.
> Therefore, adding a go.mod file to each module would allow qpid proton go
> bindings to be managed as a go module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2105) Support Go modules
[
https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16941458#comment-16941458
]
Roddie Kieley commented on PROTON-2105:
---
As there should be [one module with multiple
packages|https://golang.org/cmd/go/#hdr-Modules__module_versions__and_more],
having a go.mod file in the Qpid-proton directory itself as per this scratch
PROTON-2105
[go.mod|https://github.com/RoddieKieley/qpid-proton/blob/PROTON-2105/go.mod]
file works ok:
{noformat}
module github.com/roddiekieley/qpid-proton
go 1.13
{noformat}
with the following from the referring project
{noformat}
require github.com/roddiekieley/qpid-proton v0.0.0-20191001011843-ff30eeda56ab
{noformat}
where the v0.0.0-20191001011843-ff30eeda56ab was the specific PROTON-2105
branch commit that had the above go.mod. The specific amqp package was then
imported via:
{noformat}
import (
"github.com/roddiekieley/qpid-proton/go/src/qpid.apache.org/amqp"
)
{noformat}
While that works, it is a bit absolute and verbose even with the requisite
change to apache, so needs to be simplified some more.
> Support Go modules
> --
>
> Key: PROTON-2105
> URL: https://issues.apache.org/jira/browse/PROTON-2105
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
>Reporter: Ulf Lilleengen
>Assignee: Roddie Kieley
>Priority: Major
>
> As of Go 1.12, go module support is available. In order to manage
> dependencies using go modules, dependencies must also be using go modules.
> Therefore, adding a go.mod file to each module would allow qpid proton go
> bindings to be managed as a go module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2105) Support Go modules
[
https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16940601#comment-16940601
]
Roddie Kieley commented on PROTON-2105:
---
[~lulf] Took a look. Imported your branch via
{noformat}
module modProject0
require github.com/lulf/qpid-proton PROTON-2105
go 1.13
{noformat}
which go changed to
{noformat}
module modProject0
require github.com/lulf/qpid-proton v0.0.0-20190921201711-83131bc3495d //
indirect
go 1.13
{noformat}
No problem's for 'go get' to get it however atm there's a 'next step' that's
not in place:
{noformat}
i7mbp:modProject0 rkieley$ go mod why
go: finding qpid.apache.org latest
modProject0/pkg imports
qpid.apache.org/amqp: module qpid.apache.org@latest
(v0.0.0-20190926195055-822413ea1ac9) found, but does not contain package
qpid.apache.org/amqp
modProject0/pkg imports
qpid.apache.org/electron: module qpid.apache.org@latest
(v0.0.0-20190926195055-822413ea1ac9) found, but does not contain package
qpid.apache.org/electron
i7mbp:modProject0 rkieley$ go mod graph
modProject0 github.com/lulf/qpid-proton@v0.0.0-20190921201711-83131bc3495d
i7mbp:modProject0 rkieley$
{noformat}
> Support Go modules
> --
>
> Key: PROTON-2105
> URL: https://issues.apache.org/jira/browse/PROTON-2105
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
>Reporter: Ulf Lilleengen
>Assignee: Roddie Kieley
>Priority: Major
>
> As of Go 1.12, go module support is available. In order to manage
> dependencies using go modules, dependencies must also be using go modules.
> Therefore, adding a go.mod file to each module would allow qpid proton go
> bindings to be managed as a go module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2105) Support Go modules
[ https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937971#comment-16937971 ] Roddie Kieley commented on PROTON-2105: --- [~lulf] Will take a look at your PR when I get a chance. > Support Go modules > -- > > Key: PROTON-2105 > URL: https://issues.apache.org/jira/browse/PROTON-2105 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Ulf Lilleengen >Assignee: Roddie Kieley >Priority: Major > > As of Go 1.12, go module support is available. In order to manage > dependencies using go modules, dependencies must also be using go modules. > Therefore, adding a go.mod file to each module would allow qpid proton go > bindings to be managed as a go module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2107) Go module support
[ https://issues.apache.org/jira/browse/PROTON-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937969#comment-16937969 ] Roddie Kieley commented on PROTON-2107: --- This potentially duplicates PROTON-2105, although will wait until I get a chance to take a look / reproduce before marking it a duplicate for sure. > Go module support > - > > Key: PROTON-2107 > URL: https://issues.apache.org/jira/browse/PROTON-2107 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Affects Versions: proton-c-0.29.0 >Reporter: Thtiphong Anansukkasem >Assignee: Roddie Kieley >Priority: Major > > I found the error , when i run "go get" command in go module enabled project > $go get -v qpid.apache.org/electron > go: finding qpid.apache.org latest > go get qpid.apache.org/electron: module qpid.apache.org@upgrade > (v0.0.0-20190919033840-551513f49822) found, but does not contain package > qpid.apache.org/electron > $ go get -v qpid.apache.org/amqp > go: finding qpid.apache.org latest > go get qpid.apache.org/amqp: module qpid.apache.org@upgrade > (v0.0.0-20190919033840-551513f49822) found, but does not contain package > qpid.apache.org/amqp > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2107) Go module support
[ https://issues.apache.org/jira/browse/PROTON-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roddie Kieley reassigned PROTON-2107: - Assignee: Roddie Kieley > Go module support > - > > Key: PROTON-2107 > URL: https://issues.apache.org/jira/browse/PROTON-2107 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Affects Versions: proton-c-0.29.0 >Reporter: Thtiphong Anansukkasem >Assignee: Roddie Kieley >Priority: Major > > I found the error , when i run "go get" command in go module enabled project > $go get -v qpid.apache.org/electron > go: finding qpid.apache.org latest > go get qpid.apache.org/electron: module qpid.apache.org@upgrade > (v0.0.0-20190919033840-551513f49822) found, but does not contain package > qpid.apache.org/electron > $ go get -v qpid.apache.org/amqp > go: finding qpid.apache.org latest > go get qpid.apache.org/amqp: module qpid.apache.org@upgrade > (v0.0.0-20190919033840-551513f49822) found, but does not contain package > qpid.apache.org/amqp > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2105) Support Go modules
[ https://issues.apache.org/jira/browse/PROTON-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roddie Kieley reassigned PROTON-2105: - Assignee: Roddie Kieley > Support Go modules > -- > > Key: PROTON-2105 > URL: https://issues.apache.org/jira/browse/PROTON-2105 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Ulf Lilleengen >Assignee: Roddie Kieley >Priority: Major > > As of Go 1.12, go module support is available. In order to manage > dependencies using go modules, dependencies must also be using go modules. > Therefore, adding a go.mod file to each module would allow qpid proton go > bindings to be managed as a go module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2090) [macOS] Update Travis CI for latest macOS Mojave 10.14.z
Roddie Kieley created PROTON-2090: - Summary: [macOS] Update Travis CI for latest macOS Mojave 10.14.z Key: PROTON-2090 URL: https://issues.apache.org/jira/browse/PROTON-2090 Project: Qpid Proton Issue Type: Improvement Components: build Reporter: Roddie Kieley Assignee: Roddie Kieley At the moment the Travis CI is configured for macOS 10.12/Xcode 8.3 at the low end and 10.13/Xcode10.1 at the upper end, while the latest available is 10.14/Xcode11. It may be beneficial to update the travis configuration to utilize the new upper end configuration. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-522) Apache Qpid Proton on Mac/OSX - C/Objective-C
[ https://issues.apache.org/jira/browse/PROTON-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roddie Kieley closed PROTON-522. Resolution: Implemented Assignee: Roddie Kieley Fix Version/s: proton-c-0.19.0 [~justi9] While there are many improvements that can be made, the basic functionality works as advertised. As well a MacPorts Portfile has been added for [qpid-proton|https://github.com/macports/macports-ports/blob/v2.5.0-archive/net/qpid-proton/Portfile] that has been actively [maintained|https://github.com/macports/macports-ports/pulls?utf8=%E2%9C%93=is%3Apr+is%3Aclosed+qpid-proton] since 0.19.0. Closing. > Apache Qpid Proton on Mac/OSX - C/Objective-C > - > > Key: PROTON-522 > URL: https://issues.apache.org/jira/browse/PROTON-522 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c >Reporter: Guy Dillen >Assignee: Roddie Kieley >Priority: Major > Labels: osx > Fix For: proton-c-0.19.0 > > > I would like using Apache Qpid Proton-C from a C or Objective-C application > on Mac/OSX to connect as a client to Windows Azure Service Bus. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2013) [OSX] Travis CI xcode7.3 10.11 image fails to run
[
https://issues.apache.org/jira/browse/PROTON-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley resolved PROTON-2013.
---
Resolution: Fixed
Original problem was transient although brew was still warning loudly regarding
10.11. With xcode8.3 instead of xcode7.3 10.12 is used and the loud warning is
gone.
> [OSX] Travis CI xcode7.3 10.11 image fails to run
> -
>
> Key: PROTON-2013
> URL: https://issues.apache.org/jira/browse/PROTON-2013
> Project: Qpid Proton
> Issue Type: Bug
>Reporter: Roddie Kieley
>Assignee: Roddie Kieley
>Priority: Major
>
> At the moment the travis ci macOS
> [job|https://travis-ci.org/apache/qpid-proton/jobs/498838017] for xcode7.3
> fails to run. This travis macOS image is based on 10.11 and the configuration
> utilizes brew to install required packages.
> The brew package install fails with
> {code:java}
> Error: You are using macOS 10.11.
> We (and Apple) do not provide support for this old version.
> You will encounter build failures with some formulae.
> Please create pull requests instead of asking for help on Homebrew's GitHub,
> Discourse, Twitter or IRC. You are responsible for resolving any issues you
> experience, as you are running this old version.
> Error: Your Xcode (7.3.1) is outdated.
> Please update to Xcode 8.2.1 (or delete it).
> Xcode can be updated from the App Store.
> Error: A newer Command Line Tools release is available.
> Update them from Software Update in the App Store.
> The command "brew install libuv swig" failed and exited with 1 during .
> Your build has been stopped.{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2013) [OSX] Travis CI xcode7.3 10.11 image fails to run
[
https://issues.apache.org/jira/browse/PROTON-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781619#comment-16781619
]
Roddie Kieley commented on PROTON-2013:
---
Work begun on my PROTON-2013
[branch|https://github.com/RoddieKieley/qpid-proton/tree/PROTON-2013]. At the
moment it looks like the xcode10.1
[job|https://travis-ci.org/RoddieKieley/qpid-proton/jobs/500132584] has some
issues that need to be addressed.
> [OSX] Travis CI xcode7.3 10.11 image fails to run
> -
>
> Key: PROTON-2013
> URL: https://issues.apache.org/jira/browse/PROTON-2013
> Project: Qpid Proton
> Issue Type: Bug
>Reporter: Roddie Kieley
>Assignee: Roddie Kieley
>Priority: Major
>
> At the moment the travis ci macOS
> [job|https://travis-ci.org/apache/qpid-proton/jobs/498838017] for xcode7.3
> fails to run. This travis macOS image is based on 10.11 and the configuration
> utilizes brew to install required packages.
> The brew package install fails with
> {code:java}
> Error: You are using macOS 10.11.
> We (and Apple) do not provide support for this old version.
> You will encounter build failures with some formulae.
> Please create pull requests instead of asking for help on Homebrew's GitHub,
> Discourse, Twitter or IRC. You are responsible for resolving any issues you
> experience, as you are running this old version.
> Error: Your Xcode (7.3.1) is outdated.
> Please update to Xcode 8.2.1 (or delete it).
> Xcode can be updated from the App Store.
> Error: A newer Command Line Tools release is available.
> Update them from Software Update in the App Store.
> The command "brew install libuv swig" failed and exited with 1 during .
> Your build has been stopped.{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2013) [OSX] Travis CI xcode7.3 10.11 image fails to run
Roddie Kieley created PROTON-2013:
-
Summary: [OSX] Travis CI xcode7.3 10.11 image fails to run
Key: PROTON-2013
URL: https://issues.apache.org/jira/browse/PROTON-2013
Project: Qpid Proton
Issue Type: Bug
Reporter: Roddie Kieley
Assignee: Roddie Kieley
At the moment the travis ci macOS
[job|https://travis-ci.org/apache/qpid-proton/jobs/498838017] for xcode7.3
fails to run. This travis macOS image is based on 10.11 and the configuration
utilizes brew to install required packages.
The brew package install fails with
{code:java}
Error: You are using macOS 10.11.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Discourse, Twitter or IRC. You are responsible for resolving any issues you
experience, as you are running this old version.
Error: Your Xcode (7.3.1) is outdated.
Please update to Xcode 8.2.1 (or delete it).
Xcode can be updated from the App Store.
Error: A newer Command Line Tools release is available.
Update them from Software Update in the App Store.
The command "brew install libuv swig" failed and exited with 1 during .
Your build has been stopped.{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1957) [OSX] re-enable python tests in Travis CI for xcode7.3
Roddie Kieley created PROTON-1957: - Summary: [OSX] re-enable python tests in Travis CI for xcode7.3 Key: PROTON-1957 URL: https://issues.apache.org/jira/browse/PROTON-1957 Project: Qpid Proton Issue Type: Task Components: build Affects Versions: proton-c-0.26.0 Environment: Travis CI xcode7.3 image Reporter: Roddie Kieley Looking at the logs for the macOS Travis CI job covering [Xcode 7.3|https://travis-ci.org/apache/qpid-proton/jobs/440387457] we see that the python tests do not execute at the moment. This occurred due to removing the brew python upgrade which installed a non-functional python 3.7.0 installation. Removal resulted in a successful build and test, minus other issues, but did disable the python tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1805) [MacOS] Fuzzer issues in fuzz-connection-driver & fuzz-message-decode
[
https://issues.apache.org/jira/browse/PROTON-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427818#comment-16427818
]
Roddie Kieley commented on PROTON-1805:
---
[~gemmellr] That's interesting re: the os version discrepancy and could be an
issue. [~astitcher] I previously had indeed tested with FUZZ_LONG_TESTS ON but
tested again tonight without it ON and do not see SegFaults but see that the
fuzz tests pass.
{code:java}
.
.
.
27: Test command:
/Users/rkieley/LocalProjects/apache/qp-040518-0/proton-c/src/tests/fuzz/fuzz-sniff-header
27: Test timeout computed to be: 1500
27: StandaloneFuzzTargetMain: running 0 inputs
4/4 Test #27: fuzz-sniff-header Passed 0.01 sec
The following tests passed:
fuzz-connection-driver
fuzz-message-decode
fuzz-url
fuzz-sniff-header
100% tests passed, 0 tests failed out of 4
Total Test time (real) = 0.75 sec
{code}
Ran ctest -VV -R fuzz a few times to see if it would change but the result was
consistent.
> [MacOS] Fuzzer issues in fuzz-connection-driver & fuzz-message-decode
> -
>
> Key: PROTON-1805
> URL: https://issues.apache.org/jira/browse/PROTON-1805
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Reporter: Andrew Stitcher
>Priority: Major
> Labels: fuzzer, mac-os-x, osx
>
> Introducing the fuzz tester has shown up a couple of segvs in the MacOS port.
> for fuzz-connection-driver:
> {noformat}
> 26: Running:
> /Users/travis/build/astitcher/qpid-proton/proton-c/src/tests/fuzz/fuzz-connection-driver/corpus/7e51d07e16f84d001a8be4a1dedf556b3b16720c
> 26/34 Test #26: fuzz-connection-driver ...***Exception: SegFault
> 1.76 sec{noformat}
> and for fuzz-message-decode:
> {noformat}
> 27: Running:
> /Users/travis/build/astitcher/qpid-proton/proton-c/src/tests/fuzz/fuzz-message-decode/corpus/d5143aaeea6897d4264440017cd47ebc874f4440
> 27/34 Test #27: fuzz-message-decode ..***Exception: SegFault
> 1.97 sec{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1805) [MacOS] Fuzzer issues in fuzz-connection-driver & fuzz-message-decode
[
https://issues.apache.org/jira/browse/PROTON-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413247#comment-16413247
]
Roddie Kieley commented on PROTON-1805:
---
Which version(s) of macOS were you testing with? On 10.11.6 with Xcode 7.3.1
I'm seeing:
{code:java}
Scanning dependencies of target fuzz-proactor-receive
[ 74%] Building C object
proton-c/src/tests/fuzz/CMakeFiles/fuzz-proactor-receive.dir/fuzz-proactor-receive.c.o
/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/src/tests/fuzz/fuzz-proactor-receive.c:184:7:
warning: implicit declaration of function 'clock_gettime' is invalid in C99
[-Wimplicit-function-declaration]
if (clock_gettime(CLOCK_MONOTONIC, ) != 0) {
^
/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/src/tests/fuzz/fuzz-proactor-receive.c:184:21:
error: use of undeclared identifier 'CLOCK_MONOTONIC'
if (clock_gettime(CLOCK_MONOTONIC, ) != 0) {
^
/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/src/tests/fuzz/fuzz-proactor-receive.c:268:5:
warning: implicit declaration of function 'kill' is invalid in C99
[-Wimplicit-function-declaration]
kill(getppid(), SIGUSR1);
^
/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/src/tests/fuzz/fuzz-proactor-receive.c:315:3:
warning: implicit declaration of function 'sigemptyset' is invalid in C99
[-Wimplicit-function-declaration]
sigemptyset(_mask);
^
/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/src/tests/fuzz/fuzz-proactor-receive.c:317:7:
warning: implicit declaration of function 'sigaction' is invalid in C99
[-Wimplicit-function-declaration]
if (sigaction(SIGUSR1, , NULL) == -1) {
^
4 warnings and 1 error generated.
{code}
Once rectified via the MIT licensed
[mach_gettime|https://gist.github.com/alfwatt/3588c5aa1f7a1ef7a3bb] replacement
I see:
{code}
23/30 Test #23: fuzz-connection-driver ... Passed0.40 sec
test 24
Start 24: fuzz-message-decode
.
.
.
24/30 Test #24: fuzz-message-decode .. Passed0.30 sec
test 25
{code}
Did it take a number of times before it failed?
> [MacOS] Fuzzer issues in fuzz-connection-driver & fuzz-message-decode
> -
>
> Key: PROTON-1805
> URL: https://issues.apache.org/jira/browse/PROTON-1805
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Reporter: Andrew Stitcher
>Priority: Major
> Labels: fuzzer, mac-os-x, osx
>
> Introducing the fuzz tester has shown up a couple of segvs in the MacOS port.
> for fuzz-connection-driver:
> {noformat}
> 26: Running:
> /Users/travis/build/astitcher/qpid-proton/proton-c/src/tests/fuzz/fuzz-connection-driver/corpus/7e51d07e16f84d001a8be4a1dedf556b3b16720c
> 26/34 Test #26: fuzz-connection-driver ...***Exception: SegFault
> 1.76 sec{noformat}
> and for fuzz-message-decode:
> {noformat}
> 27: Running:
> /Users/travis/build/astitcher/qpid-proton/proton-c/src/tests/fuzz/fuzz-message-decode/corpus/d5143aaeea6897d4264440017cd47ebc874f4440
> 27/34 Test #27: fuzz-message-decode ..***Exception: SegFault
> 1.97 sec{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1695) [OSX] Cyrus SASL plugins do not load leading to missing mechanisms
[
https://issues.apache.org/jira/browse/PROTON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412854#comment-16412854
]
Roddie Kieley commented on PROTON-1695:
---
In doing some follow up work on this I first ran into:
{code:java}
1: proton_tests.reactor.ApplicationEventTest.test_application_events ...
pass
1: proton_tests.reactor.ContainerTest. \
1: test_authentication_via_container_attributes
start
1: 2018-03-24 22:39:54,593 ERROR proton:io:sasl_error: SASL(-13): user not
found: no secret in database (Failed to authenticate client [mech=DIGEST-MD5])
1: 2018-03-24 22:39:54,595 ERROR amqp:unauthorized-access: Authentication
failed [mech=DIGEST-MD5] (connection aborted)
1: 2018-03-24 22:39:54,596 ERROR amqp:unauthorized-access: Authentication
failed [mech=DIGEST-MD5] (connection aborted)
1: proton_tests.reactor.ContainerTest. \
1: test_authentication_via_container_attributes
fail
1: Error during test: Traceback (most recent call last):
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/tests/python/proton-test",
line 365, in run
1: phase()
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/tests/python/proton_tests/reactor.py",
line 395, in test_authentication_via_container_attributes
1: container.run()
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/reactor.py",
line 148, in run
1: while self.process(): pass
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/reactor.py",
line 174, in process
1: self._check_errors()
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/reactor.py",
line 170, in _check_errors
1: _compat.raise_(exc, value, tb)
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/__init__.py",
line 4081, in dispatch
1: ev.dispatch(self.handler)
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/__init__.py",
line 3990, in dispatch
1: result = dispatch(handler, type.method, self)
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/__init__.py",
line 3868, in dispatch
1: return m(*args)
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/handlers.py",
line 418, in on_transport_error
1: event.connection.close()
1: AttributeError: 'NoneType' object has no attribute 'close'
1: proton_tests.reactor.ContainerTest.test_authentication_via_kwargs ...
start
1: 2018-03-24 22:39:54,634 ERROR proton:io:sasl_error: SASL(-13): user not
found: no secret in database (Failed to authenticate client [mech=DIGEST-MD5])
1: 2018-03-24 22:39:54,636 ERROR amqp:unauthorized-access: Authentication
failed [mech=DIGEST-MD5] (connection aborted)
1: 2018-03-24 22:39:54,637 ERROR amqp:unauthorized-access: Authentication
failed [mech=DIGEST-MD5] (connection aborted)
1: proton_tests.reactor.ContainerTest.test_authentication_via_kwargs ...
fail
1: Error during test: Traceback (most recent call last):
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/tests/python/proton-test",
line 365, in run
1: phase()
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/tests/python/proton_tests/reactor.py",
line 403, in test_authentication_via_kwargs
1: container.run()
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/reactor.py",
line 148, in run
1: while self.process(): pass
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/reactor.py",
line 174, in process
1: self._check_errors()
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/reactor.py",
line 170, in _check_errors
1: _compat.raise_(exc, value, tb)
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/__init__.py",
line 4081, in dispatch
1: ev.dispatch(self.handler)
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/__init__.py",
line 3990, in dispatch
1: result = dispatch(handler, type.method, self)
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/__init__.py",
line 3868, in dispatch
1: return m(*args)
1: File
"/Users/rkieley/LocalProjects/apache/qpid-proton/proton-c/bindings/python/proton/handlers.py",
line 418, in on_transport_error
1: event.connection.close()
1: AttributeError: 'NoneType' object has no attribute 'close'
1: proton_tests.reactor.ContainerTest.test_authentication_via_url ..
start
1: 2018-03-24 22:39:54,672 ERROR proton:io:sasl_error: SASL(-13): user not
found: no
[jira] [Commented] (PROTON-1787) [OSX] Travis CI failure to execute for Xcode 7.3 matrix'd build
[
https://issues.apache.org/jira/browse/PROTON-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390158#comment-16390158
]
Roddie Kieley commented on PROTON-1787:
---
Updated the travis yaml via PR
[139|https://github.com/apache/qpid-proton/pull/139]
> [OSX] Travis CI failure to execute for Xcode 7.3 matrix'd build
> ---
>
> Key: PROTON-1787
> URL: https://issues.apache.org/jira/browse/PROTON-1787
> Project: Qpid Proton
> Issue Type: Task
> Environment: Travis CI
>Reporter: Roddie Kieley
>Priority: Major
>
> Recently the Travis CI build for 'Compiler: gcc Xcode: xcode7.3 C++' started
> failing due to the following:
> {code:java}
> .
> .
> .
> $ export CXX=g++
> $ export CC=gcc
> $ gcc --version
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 7.3.0 (clang-703.0.31)
> Target: x86_64-apple-darwin15.6.0
> Thread model: posix
> InstalledDir:
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> before_install.1
> 296.52s$ brew update
> 66.75s$ brew upgrade python openssl
> 0.02s$ pip2 install --user --upgrade pip
> /Users/travis/.travis/job_stages: line 57: pip2: command not found
> The command "pip2 install --user --upgrade pip" failed and exited with 127
> during .
> Your build has been stopped.{code}
>
> This appears to be due to a recent change in homebrew whereby installing
> 'python' installed python 2 but now installs python 3.
> From a previous, working, travis
> [job|https://travis-ci.org/RoddieKieley/qpid-proton/jobs/327960307]
> {code}
> $ brew upgrade python openssl
> ==> Upgrading 2 outdated packages, with result:
> python 2.7.14_2, openssl 1.0.2n
> {code}
> From the latest [job|https://travis-ci.org/apache/qpid-proton/jobs/349877911]
> that's broken:
> {code}
> $ brew upgrade python openssl
> ==> Upgrading 2 outdated packages, with result:
> python 3.6.4_3, openssl 1.0.2n
> {code}
> Looking on http://formulae.brew.sh/ we see:
> {code}
> Recently removed formulae
> python3, php72-opcache, php72-snmp, php72-tidy, php72
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1787) [OSX] Travis CI failure to execute for Xcode 7.3 matrix'd build
Roddie Kieley created PROTON-1787:
-
Summary: [OSX] Travis CI failure to execute for Xcode 7.3 matrix'd
build
Key: PROTON-1787
URL: https://issues.apache.org/jira/browse/PROTON-1787
Project: Qpid Proton
Issue Type: Task
Environment: Travis CI
Reporter: Roddie Kieley
Recently the Travis CI build for 'Compiler: gcc Xcode: xcode7.3 C++' started
failing due to the following:
{code:java}
.
.
.
$ export CXX=g++
$ export CC=gcc
$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 7.3.0 (clang-703.0.31)
Target: x86_64-apple-darwin15.6.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
before_install.1
296.52s$ brew update
66.75s$ brew upgrade python openssl
0.02s$ pip2 install --user --upgrade pip
/Users/travis/.travis/job_stages: line 57: pip2: command not found
The command "pip2 install --user --upgrade pip" failed and exited with 127
during .
Your build has been stopped.{code}
This appears to be due to a recent change in homebrew whereby installing
'python' installed python 2 but now installs python 3.
>From a previous, working, travis
>[job|https://travis-ci.org/RoddieKieley/qpid-proton/jobs/327960307]
{code}
$ brew upgrade python openssl
==> Upgrading 2 outdated packages, with result:
python 2.7.14_2, openssl 1.0.2n
{code}
>From the latest [job|https://travis-ci.org/apache/qpid-proton/jobs/349877911]
>that's broken:
{code}
$ brew upgrade python openssl
==> Upgrading 2 outdated packages, with result:
python 3.6.4_3, openssl 1.0.2n
{code}
Looking on http://formulae.brew.sh/ we see:
{code}
Recently removed formulae
python3, php72-opcache, php72-snmp, php72-tidy, php72
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1732) [OSX] Enable swig for the Travis CI build
[ https://issues.apache.org/jira/browse/PROTON-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roddie Kieley resolved PROTON-1732. --- Resolution: Resolved PR updated and committed with assistance from [~astitcher]. > [OSX] Enable swig for the Travis CI build > - > > Key: PROTON-1732 > URL: https://issues.apache.org/jira/browse/PROTON-1732 > Project: Qpid Proton > Issue Type: Sub-task > Components: proton-c >Affects Versions: proton-c-0.19.0 > Environment: Travis CI > Xcode 7.3, 9 >Reporter: Roddie Kieley >Priority: Minor > Fix For: proton-c-future > > > Comparing the current travis builds for linux and osx we see that the linux > builds cover ruby whereas the osx builds do not. Swig is required for this to > occur. -- 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] [Created] (PROTON-1732) [OSX] Enable swig for the Travis CI build
Roddie Kieley created PROTON-1732: - Summary: [OSX] Enable swig for the Travis CI build Key: PROTON-1732 URL: https://issues.apache.org/jira/browse/PROTON-1732 Project: Qpid Proton Issue Type: Sub-task Affects Versions: proton-c-0.19.0 Environment: Travis CI Xcode 7.3, 9 Reporter: Roddie Kieley Priority: Minor Comparing the current travis builds for linux and osx we see that the linux builds cover ruby whereas the osx builds do not. Swig is required for this to occur. -- 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] [Resolved] (PROTON-1729) [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version
[ https://issues.apache.org/jira/browse/PROTON-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roddie Kieley resolved PROTON-1729. --- Resolution: Done > [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version > --- > > Key: PROTON-1729 > URL: https://issues.apache.org/jira/browse/PROTON-1729 > Project: Qpid Proton > Issue Type: Improvement >Affects Versions: proton-c-0.19.0 > Environment: OSX 10.11.6 > Xcode 7.3.1 >Reporter: Roddie Kieley >Priority: Minor > > The release of 0.19.0 marks the first official tagged release that builds on > OSX "out of the box". A MacPorts Portfile for Qpid Proton was added as soon > as a commit became available that would build on OSX in the 0.18.1++ > timeframe and this should be updated to utilize the 0.19.0 release. -- 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-1729) [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version
[ https://issues.apache.org/jira/browse/PROTON-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310551#comment-16310551 ] Roddie Kieley commented on PROTON-1729: --- PR [#1163|https://github.com/macports/macports-ports/pull/1163] merged to macports:master after successful [travis ci|https://travis-ci.org/macports/macports-ports/jobs/322752858] build. > [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version > --- > > Key: PROTON-1729 > URL: https://issues.apache.org/jira/browse/PROTON-1729 > Project: Qpid Proton > Issue Type: Improvement >Affects Versions: proton-c-0.19.0 > Environment: OSX 10.11.6 > Xcode 7.3.1 >Reporter: Roddie Kieley >Priority: Minor > > The release of 0.19.0 marks the first official tagged release that builds on > OSX "out of the box". A MacPorts Portfile for Qpid Proton was added as soon > as a commit became available that would build on OSX in the 0.18.1++ > timeframe and this should be updated to utilize the 0.19.0 release. -- 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-1729) [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version
[ https://issues.apache.org/jira/browse/PROTON-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305012#comment-16305012 ] Roddie Kieley commented on PROTON-1729: --- [MacPorts|http://macports.org/] [macports-ports|https://github.com/macports/macports-ports] PR [#1163|https://github.com/macports/macports-ports/pull/1163] opened for the update. > [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version > --- > > Key: PROTON-1729 > URL: https://issues.apache.org/jira/browse/PROTON-1729 > Project: Qpid Proton > Issue Type: Improvement >Affects Versions: proton-c-0.19.0 > Environment: OSX 10.11.6 > Xcode 7.3.1 >Reporter: Roddie Kieley >Priority: Minor > > The release of 0.19.0 marks the first official tagged release that builds on > OSX "out of the box". A MacPorts Portfile for Qpid Proton was added as soon > as a commit became available that would build on OSX in the 0.18.1++ > timeframe and this should be updated to utilize the 0.19.0 release. -- 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] [Created] (PROTON-1729) [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version
Roddie Kieley created PROTON-1729: - Summary: [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version Key: PROTON-1729 URL: https://issues.apache.org/jira/browse/PROTON-1729 Project: Qpid Proton Issue Type: Improvement Affects Versions: proton-c-0.19.0 Environment: OSX 10.11.6 Xcode 7.3.1 Reporter: Roddie Kieley Priority: Minor The release of 0.19.0 marks the first official tagged release that builds on OSX "out of the box". A MacPorts Portfile for Qpid Proton was added as soon as a commit became available that would build on OSX in the 0.18.1++ timeframe and this should be updated to utilize the 0.19.0 release. -- 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] [Closed] (PROTON-1701) [OSX] Add Qpid Proton to the MacPorts collection
[
https://issues.apache.org/jira/browse/PROTON-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley closed PROTON-1701.
-
Resolution: Done
MacPorts pull request
[#1070|https://github.com/macports/macports-ports/pull/1070] successfully
merged and closed.
> [OSX] Add Qpid Proton to the MacPorts collection
>
>
> Key: PROTON-1701
> URL: https://issues.apache.org/jira/browse/PROTON-1701
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Environment: OSX 10.11.6
> MacPorts 2.4.z
>Reporter: Roddie Kieley
>Priority: Minor
>
> According to [The MacPorts Project Official
> Homepage|https://www.macports.org/]:
> {quote}
> The MacPorts Project is an open-source community initiative to design an
> easy-to-use system for compiling, installing, and upgrading either
> command-line, X11 or Aqua based open-source software on the Mac operating
> system.
> {quote}
> As such it would be beneficial for the open-source community if Qpid Proton
> was a part of the collection so that it was easily consumable on OSX.
--
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] [Closed] (PROTON-1711) SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails
[
https://issues.apache.org/jira/browse/PROTON-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley closed PROTON-1711.
-
Just got latest master and works for me now - closing - thanks [~astitcher]!
> SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails
> --
>
> Key: PROTON-1711
> URL: https://issues.apache.org/jira/browse/PROTON-1711
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Environment: Fedora 25
> OSX 10.11.6
>Reporter: Roddie Kieley
>Assignee: Andrew Stitcher
> Fix For: proton-c-0.19.0
>
>
> When building a default build via 'cmake ../qpid-proton' everything builds as
> expected. However after using 'ccmake ../qpid-proton' and setting SSL_IMPL to
> none we see:
> Fedora 25
> {code}
> .
> .
> .
> [ 76%] Linking C executable c-data-tests
> [ 76%] Built target c-data-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> CMakeFiles/c-ssl-tests.dir/ssl.c.o: In function `test_ssl_protocols':
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:29:
> undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:31:
> undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:33:
> undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:36:
> undefined reference to `pn_ssl_domain_set_protocols'
> /home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:37:
> undefined reference to `pn_ssl_domain_set_protocols'
> CMakeFiles/c-ssl-tests.dir/ssl.c.o:/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:38:
> more undefined references to `pn_ssl_domain_set_protocols' follow
> collect2: error: ld returned 1 exit status
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:95: recipe for
> target 'proton-c/src/tests/c-ssl-tests' failed
> gmake[2]: *** [proton-c/src/tests/c-ssl-tests] Error 1
> CMakeFiles/Makefile2:2435: recipe for target
> 'proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all' failed
> gmake[1]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> Makefile:140: recipe for target 'all' failed
> gmake: *** [all] Error 2
> [rkieley@i7t450s 6]$
> {code}
> OSX 10.11.6
> {code}
> .
> .
> .
> [ 76%] Building C object
> proton-c/src/tests/CMakeFiles/c-engine-tests.dir/engine.c.o
> [ 76%] Linking C executable c-engine-tests
> [ 76%] Built target c-engine-tests
> [ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
> [ 77%] Linking C executable c-ssl-tests
> Undefined symbols for architecture x86_64:
> "_pn_ssl_domain_set_protocols", referenced from:
> _test_ssl_protocols in ssl.c.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> gmake[2]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:96:
> proton-c/src/tests/c-ssl-tests] Error 1
> gmake[1]: *** [CMakeFiles/Makefile2:2436:
> proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
> gmake: *** [Makefile:141: all] Error 2
> earth:153 rkieley$
> {code}
> Note that I also had disabled the bindings as well as set SASL_IMPL to none.
--
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] [Created] (PROTON-1711) SSL_IMPL none SASL_IMPL none build attempts to build c-ssl-tests and fails
Roddie Kieley created PROTON-1711:
-
Summary: SSL_IMPL none SASL_IMPL none build attempts to build
c-ssl-tests and fails
Key: PROTON-1711
URL: https://issues.apache.org/jira/browse/PROTON-1711
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Environment: Fedora 25
OSX 10.11.6
Reporter: Roddie Kieley
When building a default build via 'cmake ../qpid-proton' everything builds as
expected. However after using 'ccmake ../qpid-proton' and setting SSL_IMPL to
none we see:
Fedora 25
{code}
.
.
.
[ 76%] Linking C executable c-data-tests
[ 76%] Built target c-data-tests
[ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
[ 77%] Linking C executable c-ssl-tests
CMakeFiles/c-ssl-tests.dir/ssl.c.o: In function `test_ssl_protocols':
/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:29:
undefined reference to `pn_ssl_domain_set_protocols'
/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:31:
undefined reference to `pn_ssl_domain_set_protocols'
/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:33:
undefined reference to `pn_ssl_domain_set_protocols'
/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:36:
undefined reference to `pn_ssl_domain_set_protocols'
/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:37:
undefined reference to `pn_ssl_domain_set_protocols'
CMakeFiles/c-ssl-tests.dir/ssl.c.o:/home/rkieley/LocalProjects/issues/PROTON-X/qpid-proton/proton-c/src/tests/ssl.c:38:
more undefined references to `pn_ssl_domain_set_protocols' follow
collect2: error: ld returned 1 exit status
proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:95: recipe for target
'proton-c/src/tests/c-ssl-tests' failed
gmake[2]: *** [proton-c/src/tests/c-ssl-tests] Error 1
CMakeFiles/Makefile2:2435: recipe for target
'proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all' failed
gmake[1]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
Makefile:140: recipe for target 'all' failed
gmake: *** [all] Error 2
[rkieley@i7t450s 6]$
{code}
OSX 10.11.6
{code}
.
.
.
[ 76%] Building C object
proton-c/src/tests/CMakeFiles/c-engine-tests.dir/engine.c.o
[ 76%] Linking C executable c-engine-tests
[ 76%] Built target c-engine-tests
[ 77%] Building C object proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/ssl.c.o
[ 77%] Linking C executable c-ssl-tests
Undefined symbols for architecture x86_64:
"_pn_ssl_domain_set_protocols", referenced from:
_test_ssl_protocols in ssl.c.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[2]: *** [proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/build.make:96:
proton-c/src/tests/c-ssl-tests] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:2436:
proton-c/src/tests/CMakeFiles/c-ssl-tests.dir/all] Error 2
gmake: *** [Makefile:141: all] Error 2
earth:153 rkieley$
{code}
Note that I also had disabled the bindings as well as set SASL_IMPL to none.
--
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-1701) [OSX] Add Qpid Proton to the MacPorts collection
[
https://issues.apache.org/jira/browse/PROTON-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276188#comment-16276188
]
Roddie Kieley commented on PROTON-1701:
---
MacPorts pull request
[#1070|https://github.com/macports/macports-ports/pull/1070] submitted -
pending.
> [OSX] Add Qpid Proton to the MacPorts collection
>
>
> Key: PROTON-1701
> URL: https://issues.apache.org/jira/browse/PROTON-1701
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Environment: OSX 10.11.6
> MacPorts 2.4.z
>Reporter: Roddie Kieley
>Priority: Minor
>
> According to [The MacPorts Project Official
> Homepage|https://www.macports.org/]:
> {quote}
> The MacPorts Project is an open-source community initiative to design an
> easy-to-use system for compiling, installing, and upgrading either
> command-line, X11 or Aqua based open-source software on the Mac operating
> system.
> {quote}
> As such it would be beneficial for the open-source community if Qpid Proton
> was a part of the collection so that it was easily consumable on OSX.
--
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-1701) [OSX] Add Qpid Proton to the MacPorts collection
[
https://issues.apache.org/jira/browse/PROTON-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267992#comment-16267992
]
Roddie Kieley commented on PROTON-1701:
---
Current work
[here|https://github.com/RoddieKieley/macports-ports/tree/qpid-proton/net/qpid-proton],
needs final test and cleanup prior to submission.
> [OSX] Add Qpid Proton to the MacPorts collection
>
>
> Key: PROTON-1701
> URL: https://issues.apache.org/jira/browse/PROTON-1701
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Environment: OSX 10.11.6
> MacPorts 2.4.z
>Reporter: Roddie Kieley
>Priority: Minor
>
> According to [The MacPorts Project Official
> Homepage|https://www.macports.org/]:
> {quote}
> The MacPorts Project is an open-source community initiative to design an
> easy-to-use system for compiling, installing, and upgrading either
> command-line, X11 or Aqua based open-source software on the Mac operating
> system.
> {quote}
> As such it would be beneficial for the open-source community if Qpid Proton
> was a part of the collection so that it was easily consumable on OSX.
--
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] [Created] (PROTON-1701) [OSX] Add Qpid Proton to the MacPorts collection
Roddie Kieley created PROTON-1701:
-
Summary: [OSX] Add Qpid Proton to the MacPorts collection
Key: PROTON-1701
URL: https://issues.apache.org/jira/browse/PROTON-1701
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Environment: OSX 10.11.6
MacPorts 2.4.z
Reporter: Roddie Kieley
Priority: Minor
According to [The MacPorts Project Official Homepage|https://www.macports.org/]:
{quote}
The MacPorts Project is an open-source community initiative to design an
easy-to-use system for compiling, installing, and upgrading either
command-line, X11 or Aqua based open-source software on the Mac operating
system.
{quote}
As such it would be beneficial for the open-source community if Qpid Proton was
a part of the collection so that it was easily consumable on OSX.
--
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-522) Apache Qpid Proton on Mac/OSX - C/Objective-C
[ https://issues.apache.org/jira/browse/PROTON-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265583#comment-16265583 ] Roddie Kieley commented on PROTON-522: -- [~gemmellr], [~astitcher] the local build issue looks related to an old source or include file being picked up due to the work I'm doing on a Portfile for the MacPorts collection. Now working ok here with same configuration as the travis build. > Apache Qpid Proton on Mac/OSX - C/Objective-C > - > > Key: PROTON-522 > URL: https://issues.apache.org/jira/browse/PROTON-522 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c >Reporter: Guy Dillen > Labels: osx > > I would like using Apache Qpid Proton-C from a C or Objective-C application > on Mac/OSX to connect as a client to Windows Azure Service Bus. -- 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] [Comment Edited] (PROTON-522) Apache Qpid Proton on Mac/OSX - C/Objective-C
[ https://issues.apache.org/jira/browse/PROTON-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264881#comment-16264881 ] Roddie Kieley edited comment on PROTON-522 at 11/24/17 2:53 AM: [~gemmellr], [~astitcher] I've closed the associated PR and will test Xcode 8 to see if the noted issue on master is resolved or not and file an issue accordingly. Interestingly I see that the latest apache/qpid-proton travis [job|https://travis-ci.org/apache/qpid-proton/jobs/306409455] which now includes OSX and Xcode 7.3 does not exhibit this issue. was (Author: rkieley): [~gemmellr], [~astitcher] I've closed the associated PR and will test Xcode 8 to see if the noted issue on master is resolved or not and file an issue accordingly. Interestingly I see that the latest apache/qpid-proton travis job which now includes OSX and Xcode 7.3 does not exhibit this issue. > Apache Qpid Proton on Mac/OSX - C/Objective-C > - > > Key: PROTON-522 > URL: https://issues.apache.org/jira/browse/PROTON-522 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c >Reporter: Guy Dillen > Labels: osx > > I would like using Apache Qpid Proton-C from a C or Objective-C application > on Mac/OSX to connect as a client to Windows Azure Service Bus. -- 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] [Comment Edited] (PROTON-522) Apache Qpid Proton on Mac/OSX - C/Objective-C
[ https://issues.apache.org/jira/browse/PROTON-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264881#comment-16264881 ] Roddie Kieley edited comment on PROTON-522 at 11/24/17 2:52 AM: [~gemmellr], [~astitcher] I've closed the associated PR and will test Xcode 8 to see if the noted issue on master is resolved or not and file an issue accordingly. Interestingly I see that the latest apache/qpid-proton travis job which now includes OSX and Xcode 7.3 does not exhibit this issue. was (Author: rkieley): [~gemmellr], [~astitcher] I've closed the associated PR and will test Xcode 8 to see if the noted issue on master is resolved or not and file an issue accordingly. > Apache Qpid Proton on Mac/OSX - C/Objective-C > - > > Key: PROTON-522 > URL: https://issues.apache.org/jira/browse/PROTON-522 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c >Reporter: Guy Dillen > Labels: osx > > I would like using Apache Qpid Proton-C from a C or Objective-C application > on Mac/OSX to connect as a client to Windows Azure Service Bus. -- 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-522) Apache Qpid Proton on Mac/OSX - C/Objective-C
[ https://issues.apache.org/jira/browse/PROTON-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264881#comment-16264881 ] Roddie Kieley commented on PROTON-522: -- [~gemmellr], [~astitcher] I've closed the associated PR and will test Xcode 8 to see if the noted issue on master is resolved or not and file an issue accordingly. > Apache Qpid Proton on Mac/OSX - C/Objective-C > - > > Key: PROTON-522 > URL: https://issues.apache.org/jira/browse/PROTON-522 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c >Reporter: Guy Dillen > Labels: osx > > I would like using Apache Qpid Proton-C from a C or Objective-C application > on Mac/OSX to connect as a client to Windows Azure Service Bus. -- 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] [Created] (PROTON-1695) [OSX] Cyrus SASL plugins do not load leading to missing mechanisms
Roddie Kieley created PROTON-1695:
-
Summary: [OSX] Cyrus SASL plugins do not load leading to missing
mechanisms
Key: PROTON-1695
URL: https://issues.apache.org/jira/browse/PROTON-1695
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: proton-c-0.18.0
Environment: OS X 10.11.6
Cyrus SASL 2.1.26
Reporter: Roddie Kieley
Found this issue while working on PROTON-522 as per this
[comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
the short version of which is:
{quote}
Ran into some trouble with cyrus-sasl after seeing that the go TestAuthPlain
failed for both "Unix Makefiles" and "Xcode", in this case 7.3.1. Found that
the plugins do not get loaded on OSX due to sasl_client_init(NULL) but
rectified with sasl_client_init(pni_user_password_callbacks).
{quote}
The issue with the go-test TestAuthPlain was addressed via PROTON-1655, however
the work for PROTON-522 does not include the above update as testing the update
was not complete.
--
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] [Resolved] (PROTON-1657) [OSX] cpp-container_test test_container_[default|no]_vhost() tests fail
[
https://issues.apache.org/jira/browse/PROTON-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley resolved PROTON-1657.
---
Resolution: Fixed
Followed the advice in PROTON-1064 and closed the port early for OSX via a
small update to test_port.hpp via this
[commit|https://github.com/RoddieKieley/qpid-proton/commit/1d4e3a8c4afa8165a07046416708193239edd4a0].
Tested and locally passes both test_container_default_vhost and
test_container_no_vhost as well as other sibling tests that are a part of
cpp-container_test:
{code}
8: Test command:
/Users/rkieley/LocalProjects/issues/PROTON-522/128/proton-c/bindings/cpp/container_test
8: Test timeout computed to be: 1500
8: TEST: test_container_default_container_id()
8: TEST: test_container_vhost()
8: TEST: test_container_default_vhost()
8: TEST: test_container_no_vhost()
8: TEST: test_container_bad_address()
8: TEST: test_container_stop()
8: TEST: test_container_schedule_nohang()
8: TEST: test_container_immediate_stop()
8/35 Test #8: cpp-container_test ... Passed0.30 sec
{code}
> [OSX] cpp-container_test test_container_[default|no]_vhost() tests fail
> ---
>
> Key: PROTON-1657
> URL: https://issues.apache.org/jira/browse/PROTON-1657
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: cpp-binding
> Environment: OSX 10.11.6, Xcode 7.3.1
>Reporter: Roddie Kieley
>Assignee: Cliff Jansen
>Priority: Major
>
> At the moment when the cpp-container-test tests
> test_container_default_vhost() and test_container_no_vhost() are run I see
> the following:
> {code}
> 8: TEST: test_container_default_vhost()
> 8: ERROR test_container_default_vhost()
> 8:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/cpp/src/container_test.cpp:267:
> proton:io: connection timed out - connecting to 127.0.0.1:49724
> 8: TEST: test_container_no_vhost()
> 8: ERROR test_container_no_vhost()
> 8:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/cpp/src/container_test.cpp:268:
> proton:io: connection timed out - connecting to 127.0.0.1:49730
> {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] [Comment Edited] (PROTON-1656) [OSX] c-proactor-tests test_ipv4_ipv6 fails
[
https://issues.apache.org/jira/browse/PROTON-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16234389#comment-16234389
]
Roddie Kieley edited comment on PROTON-1656 at 11/1/17 5:05 PM:
With our without the setsockopt so_reuseport using {code} close(tp.sock) {code}
as per the WIN32 {code}closesocket(tp.sock){code} in the test_port of
test_port.h allows the test to pass if ONLY test_ipv4_ipv6 is run and only if
there is a "period" of quiet previously where the test is not run. Sample set
of c-proactor-tests direct executions with just test_ipv4_ipv6:
{code}
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:648:
check failed: want PN_LISTENER_CLOSE got PN_PROACTOR_INACTIVE
[test_ipv4_ipv6()]
FAIL: test_ipv4_ipv6() (2 errors)
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
FAIL: test_ipv4_ipv6() (1 errors)
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:643:
info: skip IPv6 tests: PN_PROACTOR_INACTIVE no condition [test_ipv4_ipv6()]
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:643:
info: skip IPv6 tests: PN_PROACTOR_INACTIVE no condition [test_ipv4_ipv6()]
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:648:
check failed: want PN_LISTENER_CLOSE got PN_PROACTOR_INACTIVE
[test_ipv4_ipv6()]
FAIL: test_ipv4_ipv6() (2 errors)
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:643:
info: skip IPv6 tests: PN_TRANSPORT_CLOSED no condition [test_ipv4_ipv6()]
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:643:
info: skip IPv6 tests: PN_TRANSPORT_CLOSED no condition [test_ipv4_ipv6()]
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
earth:128 rkieley$
{code}
was (Author: rkieley):
With our without the setsockopt so_reuseport using {code} close(tp.sock) {code}
as per the WIN32 {code}closesocket(tp.socke){code} in the test_port of
test_port.h allows the test to pass if ONLY test_ipv4_ipv6 is run and only if
there is a "period" of quiet previously where the test is not run. Sample set
of c-proactor-tests direct executions with just test_ipv4_ipv6:
{code}
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:648:
check failed: want PN_LISTENER_CLOSE got PN_PROACTOR_INACTIVE
[test_ipv4_ipv6()]
FAIL: test_ipv4_ipv6() (2 errors)
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
FAIL: test_ipv4_ipv6() (1 errors)
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:643:
info: skip IPv6 tests: PN_PROACTOR_INACTIVE no condition [test_ipv4_ipv6()]
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:643:
info: skip IPv6 tests: PN_PROACTOR_INACTIVE no condition [test_ipv4_ipv6()]
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST:
[jira] [Commented] (PROTON-1656) [OSX] c-proactor-tests test_ipv4_ipv6 fails
[
https://issues.apache.org/jira/browse/PROTON-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16234389#comment-16234389
]
Roddie Kieley commented on PROTON-1656:
---
With our without the setsockopt so_reuseport using {code} close(tp.sock) {code}
as per the WIN32 {code}closesocket(tp.socke){code} in the test_port of
test_port.h allows the test to pass if ONLY test_ipv4_ipv6 is run and only if
there is a "period" of quiet previously where the test is not run. Sample set
of c-proactor-tests direct executions with just test_ipv4_ipv6:
{code}
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:648:
check failed: want PN_LISTENER_CLOSE got PN_PROACTOR_INACTIVE
[test_ipv4_ipv6()]
FAIL: test_ipv4_ipv6() (2 errors)
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
FAIL: test_ipv4_ipv6() (1 errors)
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:643:
info: skip IPv6 tests: PN_PROACTOR_INACTIVE no condition [test_ipv4_ipv6()]
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:643:
info: skip IPv6 tests: PN_PROACTOR_INACTIVE no condition [test_ipv4_ipv6()]
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:648:
check failed: want PN_LISTENER_CLOSE got PN_PROACTOR_INACTIVE
[test_ipv4_ipv6()]
FAIL: test_ipv4_ipv6() (2 errors)
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:643:
info: skip IPv6 tests: PN_TRANSPORT_CLOSED no condition [test_ipv4_ipv6()]
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:643:
info: skip IPv6 tests: PN_TRANSPORT_CLOSED no condition [test_ipv4_ipv6()]
earth:128 rkieley$ ./proton-c/src/tests/c-proactor-tests
TEST: test_ipv4_ipv6()
earth:128 rkieley$
{code}
> [OSX] c-proactor-tests test_ipv4_ipv6 fails
> ---
>
> Key: PROTON-1656
> URL: https://issues.apache.org/jira/browse/PROTON-1656
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: proton-c
> Environment: OSX 10.11.6, Xcode 7.3.1
>Reporter: Roddie Kieley
>Priority: Major
> Fix For: proton-c-0.19.0
>
>
> This fails almost 100% of the time, usually with the following:
> {code}
> 10: TEST: test_ipv4_ipv6()
> 10:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:637:
> check failed: No condition, expected :refused [test_ipv4_ipv6()]
> 10:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
> check failed: No condition, expected :refused [test_ipv4_ipv6()]
> 10: FAIL: test_ipv4_ipv6() (2 errors)
> {code}
> or
> {code}
> 10: TEST: test_ipv4_ipv6()
> 10:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:637:
> check failed: 'refused' not in 'connection timed out - connecting to
> 127.0.0.1:49446' [test_ipv4_ipv6()]
> 10: FAIL: test_ipv4_ipv6() (1 errors)
> {code}
> It passed once during testing yesterday but not sure what that is indicative
> of yet. Tested on Fedora 25 and always passes. Note that Fedora 25 is on a
> separate box and I do note that the OSX box has two 'inactive' entries in
> ifconfig which may or may not interfere with binding to 0.0.0.0 or ::1:
> {code}
> earth:126 rkieley$ ifconfig
> lo0: flags=8049 mtu 16384
> options=3
> inet6 ::1 prefixlen 128
> inet 127.0.0.1 netmask 0xff00
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> nd6
[jira] [Commented] (PROTON-1656) [OSX] c-proactor-tests test_ipv4_ipv6 fails
[
https://issues.apache.org/jira/browse/PROTON-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16233527#comment-16233527
]
Roddie Kieley commented on PROTON-1656:
---
[~aconway] good to know as I had tried adding in the so_reuseport to go along
with the so_reuseaddr setsockopt as well as adding the close socket so that
reuse wasn't a factor but haven't had much luck on tweaking the test to pass at
this point.
[~gemmellr] there's a travis CI build of the PROTON-522 branch
[here|https://travis-ci.org/RoddieKieley/qpid-proton] although for the last
little while I had inadvertently added a tab in the yaml instead of spaces so
it wasn't running. Just fixed that up and while it's not green quite yet, it's
a good start as to what's required.
> [OSX] c-proactor-tests test_ipv4_ipv6 fails
> ---
>
> Key: PROTON-1656
> URL: https://issues.apache.org/jira/browse/PROTON-1656
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: proton-c
> Environment: OSX 10.11.6, Xcode 7.3.1
>Reporter: Roddie Kieley
>Priority: Major
> Fix For: proton-c-0.19.0
>
>
> This fails almost 100% of the time, usually with the following:
> {code}
> 10: TEST: test_ipv4_ipv6()
> 10:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:637:
> check failed: No condition, expected :refused [test_ipv4_ipv6()]
> 10:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
> check failed: No condition, expected :refused [test_ipv4_ipv6()]
> 10: FAIL: test_ipv4_ipv6() (2 errors)
> {code}
> or
> {code}
> 10: TEST: test_ipv4_ipv6()
> 10:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:637:
> check failed: 'refused' not in 'connection timed out - connecting to
> 127.0.0.1:49446' [test_ipv4_ipv6()]
> 10: FAIL: test_ipv4_ipv6() (1 errors)
> {code}
> It passed once during testing yesterday but not sure what that is indicative
> of yet. Tested on Fedora 25 and always passes. Note that Fedora 25 is on a
> separate box and I do note that the OSX box has two 'inactive' entries in
> ifconfig which may or may not interfere with binding to 0.0.0.0 or ::1:
> {code}
> earth:126 rkieley$ ifconfig
> lo0: flags=8049 mtu 16384
> options=3
> inet6 ::1 prefixlen 128
> inet 127.0.0.1 netmask 0xff00
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> nd6 options=1
> gif0: flags=8010 mtu 1280
> stf0: flags=0<> mtu 1280
> en0: flags=8863 mtu 1500
> options=27
> ether d4:9a:20:0d:67:fc
> inet6 fe80::d69a:20ff:fe0d:67fc%en0 prefixlen 64 scopeid 0x4
> inet 192.168.2.4 netmask 0xff00 broadcast 192.168.2.255
> nd6 options=1
> media: autoselect (1000baseT )
> status: active
> en1: flags=8823 mtu 1500
> ether f8:1e:df:f4:46:8c
> nd6 options=1
> media: autoselect ()
> status: inactive
> fw0: flags=8863 mtu 494
> lladdr d4:9a:20:ff:fe:0d:67:fc
> nd6 options=1
> media: autoselect
> status: inactive
> earth:126 rkieley$
> {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] [Closed] (PROTON-1655) go-test TestAuthPlain fails when SASL_IMPL is none
[
https://issues.apache.org/jira/browse/PROTON-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley closed PROTON-1655.
-
> go-test TestAuthPlain fails when SASL_IMPL is none
> --
>
> Key: PROTON-1655
> URL: https://issues.apache.org/jira/browse/PROTON-1655
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
>Affects Versions: proton-c-0.18.0
> Environment: OSX 10.11.6, Xcode 7.3.1, golang 1.9.1
> Fedora 25, gcc 6.3.1, go1.7.5
>Reporter: Roddie Kieley
>Assignee: Alan Conway
> Fix For: proton-c-0.18.1
>
>
> Initially found this issue when testing the OSX work from PROTON-522, however
> after testing it fails in the same way on Fedora 25 when SASL_IMPL is none.
> As discussed in [this
> comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
> when cyrus is configured for the sasl implementation the test fails due to
> the noted sasl_client_init parameter passing.
> {code}
> 11: Test command: /opt/local/bin/python
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
> "--"
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
> "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
> -I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include"
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
> roton-c"
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
> "/opt/local/bin/go" "test" "-ldflags" "-r
> /Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race"
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.02s)
> 11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
> Authentication failed [mech=PLAIN]
> {code}
> With a sasl implementation of 'none' configured we see that it attempts to
> use mech='none' and also fails:
> {code}
> 11: Test command: /opt/local/bin/python
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
> "--"
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
> "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
> -I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include"
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
> roton-c"
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
> "/opt/local/bin/go" "test" "-ldflags" "-r
> /Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race"
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.00s)
> 11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
> Authentication failed [mech=none]
> {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-1655) go-test TestAuthPlain fails when SASL_IMPL is none
[
https://issues.apache.org/jira/browse/PROTON-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226851#comment-16226851
]
Roddie Kieley commented on PROTON-1655:
---
[~aconway] This now skips correctly for me on both OSX and Fedora 25 when
SASL_IMPL is none.
> go-test TestAuthPlain fails when SASL_IMPL is none
> --
>
> Key: PROTON-1655
> URL: https://issues.apache.org/jira/browse/PROTON-1655
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
>Affects Versions: proton-c-0.18.0
> Environment: OSX 10.11.6, Xcode 7.3.1, golang 1.9.1
> Fedora 25, gcc 6.3.1, go1.7.5
>Reporter: Roddie Kieley
>Assignee: Alan Conway
> Fix For: proton-c-0.18.1
>
>
> Initially found this issue when testing the OSX work from PROTON-522, however
> after testing it fails in the same way on Fedora 25 when SASL_IMPL is none.
> As discussed in [this
> comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
> when cyrus is configured for the sasl implementation the test fails due to
> the noted sasl_client_init parameter passing.
> {code}
> 11: Test command: /opt/local/bin/python
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
> "--"
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
> "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
> -I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include"
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
> roton-c"
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
> "/opt/local/bin/go" "test" "-ldflags" "-r
> /Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race"
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.02s)
> 11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
> Authentication failed [mech=PLAIN]
> {code}
> With a sasl implementation of 'none' configured we see that it attempts to
> use mech='none' and also fails:
> {code}
> 11: Test command: /opt/local/bin/python
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
> "--"
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
> "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
> -I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include"
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
> roton-c"
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
> "/opt/local/bin/go" "test" "-ldflags" "-r
> /Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race"
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.00s)
> 11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
> Authentication failed [mech=none]
> {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] [Comment Edited] (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 edited comment on PROTON-1658 at 10/31/17 2:11 PM:
-
[~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 any ruby tests for me on Fedora 25 atm; not sure if that is
expected behaviour for the moment.
was (Author: rkieley):
[~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=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-1657) [OSX] cpp-container_test test_container_[default|no]_vhost() tests fail
[
https://issues.apache.org/jira/browse/PROTON-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225374#comment-16225374
]
Roddie Kieley commented on PROTON-1657:
---
Focusing on just the test_container_default_vhost test with PN_TRACE_FRM=1 we
see (through the lens of lldb):
{code}
[0x1005053e0]: -> AMQP
[0x1005053e0]:0 -> @open(16) [container-id=""]
[0x1005053e0]:0 -> @close(24) [error=@error(29) [condition=:"proton:io",
description="connection timed out - connecting to 127.0.0.1:54104"]]
libc++abi.dylib: terminating with uncaught exception of type proton::error:
proton:io: connection timed out - connecting to 127.0.0.1:54104
{code}
And through the lens of netstat -p tcp -a we see (note different test run, but
consistent behaviour):
{code}
tcp4 0 0 localhost.55957localhost.55956SYN_SENT
tcp6 0 0 localhost.55956*.*LISTEN
tcp6 0 0 localhost.55956*.*LISTEN
tcp4 0 0 localhost.55956*.*CLOSED
{code}
Given the above and that the test_ipv4_ipv6 also fails, investigation on the
differences in handling a combination of ipv4 and ipv6 on OSX is required.
> [OSX] cpp-container_test test_container_[default|no]_vhost() tests fail
> ---
>
> Key: PROTON-1657
> URL: https://issues.apache.org/jira/browse/PROTON-1657
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: cpp-binding
> Environment: OSX 10.11.6, Xcode 7.3.1
>Reporter: Roddie Kieley
>Assignee: Cliff Jansen
>
> At the moment when the cpp-container-test tests
> test_container_default_vhost() and test_container_no_vhost() are run I see
> the following:
> {code}
> 8: TEST: test_container_default_vhost()
> 8: ERROR test_container_default_vhost()
> 8:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/cpp/src/container_test.cpp:267:
> proton:io: connection timed out - connecting to 127.0.0.1:49724
> 8: TEST: test_container_no_vhost()
> 8: ERROR test_container_no_vhost()
> 8:
> /Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/cpp/src/container_test.cpp:268:
> proton:io: connection timed out - connecting to 127.0.0.1:49730
> {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
[jira] [Created] (PROTON-1658) [OSX] ruby-example-test test_tools.rb initialize times out and hangs
Roddie Kieley created PROTON-1658:
-
Summary: [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] [Created] (PROTON-1657) [OSX] cpp-container_test test_container_[default|no]_vhost() tests fail
Roddie Kieley created PROTON-1657:
-
Summary: [OSX] cpp-container_test
test_container_[default|no]_vhost() tests fail
Key: PROTON-1657
URL: https://issues.apache.org/jira/browse/PROTON-1657
Project: Qpid Proton
Issue Type: Sub-task
Components: cpp-binding
Environment: OSX 10.11.6, Xcode 7.3.1
Reporter: Roddie Kieley
Assignee: Cliff Jansen
At the moment when the cpp-container-test tests test_container_default_vhost()
and test_container_no_vhost() are run I see the following:
{code}
8: TEST: test_container_default_vhost()
8: ERROR test_container_default_vhost()
8:
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/cpp/src/container_test.cpp:267:
proton:io: connection timed out - connecting to 127.0.0.1:49724
8: TEST: test_container_no_vhost()
8: ERROR test_container_no_vhost()
8:
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/cpp/src/container_test.cpp:268:
proton:io: connection timed out - connecting to 127.0.0.1:49730
{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] [Updated] (PROTON-1656) [OSX] c-proactor-tests test_ipv4_ipv6 fails
[
https://issues.apache.org/jira/browse/PROTON-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley updated PROTON-1656:
--
Description:
This fails almost 100% of the time, usually with the following:
{code}
10: TEST: test_ipv4_ipv6()
10:
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:637:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
10:
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
10: FAIL: test_ipv4_ipv6() (2 errors)
{code}
or
{code}
10: TEST: test_ipv4_ipv6()
10:
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:637:
check failed: 'refused' not in 'connection timed out - connecting to
127.0.0.1:49446' [test_ipv4_ipv6()]
10: FAIL: test_ipv4_ipv6() (1 errors)
{code}
It passed once during testing yesterday but not sure what that is indicative of
yet. Tested on Fedora 25 and always passes. Note that Fedora 25 is on a
separate box and I do note that the OSX box has two 'inactive' entries in
ifconfig which may or may not interfere with binding to 0.0.0.0 or ::1:
{code}
earth:126 rkieley$ ifconfig
lo0: flags=8049 mtu 16384
options=3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1
gif0: flags=8010 mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863 mtu 1500
options=27
ether d4:9a:20:0d:67:fc
inet6 fe80::d69a:20ff:fe0d:67fc%en0 prefixlen 64 scopeid 0x4
inet 192.168.2.4 netmask 0xff00 broadcast 192.168.2.255
nd6 options=1
media: autoselect (1000baseT )
status: active
en1: flags=8823 mtu 1500
ether f8:1e:df:f4:46:8c
nd6 options=1
media: autoselect ()
status: inactive
fw0: flags=8863 mtu 494
lladdr d4:9a:20:ff:fe:0d:67:fc
nd6 options=1
media: autoselect
status: inactive
earth:126 rkieley$
{code}
was:
This fails almost 100% of the time, usually with the following:
{code}
10: TEST: test_ipv4_ipv6()
10:
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:637:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
10:
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
10: FAIL: test_ipv4_ipv6() (2 errors)
{code}
It passed once during testing yesterday but not sure what that is indicative of
yet. Tested on Fedora 25 and always passes. Note that Fedora 25 is on a
separate box and I do note that the OSX box has two 'inactive' entries in
ifconfig which may or may not interfere with binding to 0.0.0.0 or ::1:
{code}
earth:126 rkieley$ ifconfig
lo0: flags=8049 mtu 16384
options=3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1
gif0: flags=8010 mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863 mtu 1500
options=27
ether d4:9a:20:0d:67:fc
inet6 fe80::d69a:20ff:fe0d:67fc%en0 prefixlen 64 scopeid 0x4
inet 192.168.2.4 netmask 0xff00 broadcast 192.168.2.255
nd6 options=1
media: autoselect (1000baseT )
status: active
en1: flags=8823 mtu 1500
ether f8:1e:df:f4:46:8c
nd6 options=1
media: autoselect ()
status: inactive
fw0: flags=8863 mtu 494
lladdr d4:9a:20:ff:fe:0d:67:fc
nd6 options=1
media: autoselect
status: inactive
earth:126 rkieley$
{code}
> [OSX] c-proactor-tests test_ipv4_ipv6 fails
> ---
>
> Key: PROTON-1656
> URL: https://issues.apache.org/jira/browse/PROTON-1656
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: proton-c
> Environment: OSX 10.11.6, Xcode 7.3.1
>Reporter: Roddie Kieley
>
> This fails almost 100% of the time, usually with the following:
> {code}
> 10: TEST: test_ipv4_ipv6()
> 10:
>
[jira] [Created] (PROTON-1656) [OSX] c-proactor-tests test_ipv4_ipv6 fails
Roddie Kieley created PROTON-1656:
-
Summary: [OSX] c-proactor-tests test_ipv4_ipv6 fails
Key: PROTON-1656
URL: https://issues.apache.org/jira/browse/PROTON-1656
Project: Qpid Proton
Issue Type: Sub-task
Components: proton-c
Environment: OSX 10.11.6, Xcode 7.3.1
Reporter: Roddie Kieley
This fails almost 100% of the time, usually with the following:
{code}
10: TEST: test_ipv4_ipv6()
10:
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:637:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
10:
/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/src/tests/proactor.c:638:
check failed: No condition, expected :refused [test_ipv4_ipv6()]
10: FAIL: test_ipv4_ipv6() (2 errors)
{code}
It passed once during testing yesterday but not sure what that is indicative of
yet. Tested on Fedora 25 and always passes. Note that Fedora 25 is on a
separate box and I do note that the OSX box has two 'inactive' entries in
ifconfig which may or may not interfere with binding to 0.0.0.0 or ::1:
{code}
earth:126 rkieley$ ifconfig
lo0: flags=8049 mtu 16384
options=3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1
gif0: flags=8010 mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863 mtu 1500
options=27
ether d4:9a:20:0d:67:fc
inet6 fe80::d69a:20ff:fe0d:67fc%en0 prefixlen 64 scopeid 0x4
inet 192.168.2.4 netmask 0xff00 broadcast 192.168.2.255
nd6 options=1
media: autoselect (1000baseT )
status: active
en1: flags=8823 mtu 1500
ether f8:1e:df:f4:46:8c
nd6 options=1
media: autoselect ()
status: inactive
fw0: flags=8863 mtu 494
lladdr d4:9a:20:ff:fe:0d:67:fc
nd6 options=1
media: autoselect
status: inactive
earth:126 rkieley$
{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] [Comment Edited] (PROTON-522) Apache Qpid Proton on Mac/OSX - C/Objective-C
[
https://issues.apache.org/jira/browse/PROTON-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16218540#comment-16218540
]
Roddie Kieley edited comment on PROTON-522 at 10/26/17 12:19 AM:
-
Ran into some trouble with cyrus-sasl after seeing that the go TestAuthPlain
failed for both "Unix Makefiles" and "Xcode", in this case 7.3.1. Found that
the plugins do not get loaded on OSX due to sasl_client_init(NULL) but
rectified with sasl_client_init(pni_user_password_callbacks). Tried some build
options with 2.1.26 and 2.1.27, but fell back to using the system provided
version. Either way the updated call is required and the sasl exchange takes
place ok as all mechanism plugins get loaded, however with self created sasldb
files with the correct user, fred@proton, with password xxx the plain
authentication still fails via an updated send sasl example and dispatch 0.8.0
on the other end on a Fedora 25 box.
Dropping back to setting the sasl implementation to 'none' instead of cyrus
still results in failure unfortunately:
{code}
1: --- FAIL: TestAuthPlain (0.01s)
1: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=none]
{code}
See PROTON-1655
was (Author: rkieley):
Ran into some trouble with cyrus-sasl after seeing that the go TestAuthPlain
failed for both "Unix Makefiles" and "Xcode", in this case 7.3.1. Found that
the plugins do not get loaded on OSX due to sasl_client_init(NULL) but
rectified with sasl_client_init(pni_user_password_callbacks). Tried some build
options with 2.1.26 and 2.1.27, but fell back to using the system provided
version. Either way the updated call is required and the sasl exchange takes
place ok as all mechanism plugins get loaded, however with self created sasldb
files with the correct user, fred@proton, with password xxx the plain
authentication still fails via an updated send sasl example and dispatch 0.8.0
on the other end on a Fedora 25 box.
Dropping back to setting the sasl implementation to 'none' instead of cyrus
still results in failure unfortunately:
{code}
1: --- FAIL: TestAuthPlain (0.01s)
1: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=none]
{code}
> Apache Qpid Proton on Mac/OSX - C/Objective-C
> -
>
> Key: PROTON-522
> URL: https://issues.apache.org/jira/browse/PROTON-522
> Project: Qpid Proton
> Issue Type: New Feature
> Components: proton-c
>Reporter: Guy Dillen
> Labels: osx
>
> I would like using Apache Qpid Proton-C from a C or Objective-C application
> on Mac/OSX to connect as a client to Windows Azure Service Bus.
--
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] [Updated] (PROTON-1655) go-test TestAuthPlain fails when SASL_IMPL is none
[
https://issues.apache.org/jira/browse/PROTON-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley updated PROTON-1655:
--
Issue Type: Bug (was: Sub-task)
Parent: (was: PROTON-522)
> go-test TestAuthPlain fails when SASL_IMPL is none
> --
>
> Key: PROTON-1655
> URL: https://issues.apache.org/jira/browse/PROTON-1655
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
>Affects Versions: proton-c-0.18.0
> Environment: OSX 10.11.6, Xcode 7.3.1, golang 1.9.1
> Fedora 25, gcc 6.3.1, go1.7.5
>Reporter: Roddie Kieley
>Assignee: Alan Conway
>
> Initially found this issue when testing the OSX work from PROTON-522, however
> after testing it fails in the same way on Fedora 25 when SASL_IMPL is none.
> As discussed in [this
> comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
> when cyrus is configured for the sasl implementation the test fails due to
> the noted sasl_client_init parameter passing.
> {code}
> 11: Test command: /opt/local/bin/python
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
> "--"
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
> "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
> -I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include"
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
> roton-c"
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
> "/opt/local/bin/go" "test" "-ldflags" "-r
> /Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race"
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.02s)
> 11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
> Authentication failed [mech=PLAIN]
> {code}
> With a sasl implementation of 'none' configured we see that it attempts to
> use mech='none' and also fails:
> {code}
> 11: Test command: /opt/local/bin/python
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
> "--"
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
> "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
> -I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include"
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
> roton-c"
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
> "/opt/local/bin/go" "test" "-ldflags" "-r
> /Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race"
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.00s)
> 11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
> Authentication failed [mech=none]
> {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] [Updated] (PROTON-1655) go-test TestAuthPlain fails when SASL_IMPL is none
[
https://issues.apache.org/jira/browse/PROTON-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley updated PROTON-1655:
--
Description:
Initially found this issue when testing the OSX work from PROTON-522, however
after testing it fails in the same way on Fedora 25 when SASL_IMPL is none.
As discussed in [this
comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
when cyrus is configured for the sasl implementation the test fails due to the
noted sasl_client_init parameter passing.
{code}
11: Test command: /opt/local/bin/python
"/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
"--"
"GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
"C
GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
-I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include"
"CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
roton-c"
"PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
"/opt/local/bin/go" "test" "-ldflags" "-r
/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race"
"qpid.apach
e.org/..."
.
.
.
11: === RUN TestAuthPlain
11: --- FAIL: TestAuthPlain (0.02s)
11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=PLAIN]
{code}
With a sasl implementation of 'none' configured we see that it attempts to use
mech='none' and also fails:
{code}
11: Test command: /opt/local/bin/python
"/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
"--"
"GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
"C
GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
-I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include"
"CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
roton-c"
"PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
"/opt/local/bin/go" "test" "-ldflags" "-r
/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race"
"qpid.apach
e.org/..."
.
.
.
11: === RUN TestAuthPlain
11: --- FAIL: TestAuthPlain (0.00s)
11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=none]
{code}
was:
As discussed in [this
comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
when cyrus is configured for the sasl implementation the test fails due to the
noted sasl_client_init parameter passing.
{code}
11: Test command: /opt/local/bin/python
"/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
"--"
"GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
"C
GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
-I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include"
"CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
roton-c"
"PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
"/opt/local/bin/go" "test" "-ldflags" "-r
/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race"
"qpid.apach
e.org/..."
.
.
.
11: === RUN TestAuthPlain
11: --- FAIL: TestAuthPlain (0.02s)
11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=PLAIN]
{code}
With a sasl implementation of 'none' configured we see that it attempts to use
mech='none' and also fails:
{code}
11: Test command: /opt/local/bin/python
"/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
"--"
"GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
"C
GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
-I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include"
"CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
roton-c"
"PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
"/opt/local/bin/go" "test" "-ldflags" "-r
/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race"
"qpid.apach
e.org/..."
.
.
.
11: === RUN TestAuthPlain
11: --- FAIL: TestAuthPlain (0.00s)
11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=none]
{code}
> go-test
[jira] [Updated] (PROTON-1655) go-test TestAuthPlain fails when SASL_IMPL is none
[
https://issues.apache.org/jira/browse/PROTON-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley updated PROTON-1655:
--
Environment:
OSX 10.11.6, Xcode 7.3.1, golang 1.9.1
Fedora 25, gcc 6.3.1, go1.7.5
was:OSX 10.11.6, Xcode 7.3.1
> go-test TestAuthPlain fails when SASL_IMPL is none
> --
>
> Key: PROTON-1655
> URL: https://issues.apache.org/jira/browse/PROTON-1655
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: go-binding
>Affects Versions: proton-c-0.18.0
> Environment: OSX 10.11.6, Xcode 7.3.1, golang 1.9.1
> Fedora 25, gcc 6.3.1, go1.7.5
>Reporter: Roddie Kieley
>Assignee: Alan Conway
>
> As discussed in [this
> comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
> when cyrus is configured for the sasl implementation the test fails due to
> the noted sasl_client_init parameter passing.
> {code}
> 11: Test command: /opt/local/bin/python
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
> "--"
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
> "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
> -I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include"
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
> roton-c"
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
> "/opt/local/bin/go" "test" "-ldflags" "-r
> /Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race"
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.02s)
> 11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
> Authentication failed [mech=PLAIN]
> {code}
> With a sasl implementation of 'none' configured we see that it attempts to
> use mech='none' and also fails:
> {code}
> 11: Test command: /opt/local/bin/python
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
> "--"
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
> "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
> -I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include"
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
> roton-c"
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
> "/opt/local/bin/go" "test" "-ldflags" "-r
> /Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race"
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.00s)
> 11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
> Authentication failed [mech=none]
> {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] [Updated] (PROTON-1655) go-test TestAuthPlain fails when SASL_IMPL is none
[
https://issues.apache.org/jira/browse/PROTON-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roddie Kieley updated PROTON-1655:
--
Summary: go-test TestAuthPlain fails when SASL_IMPL is none (was: [OSX]
go-test TestAuthPlain fails)
> go-test TestAuthPlain fails when SASL_IMPL is none
> --
>
> Key: PROTON-1655
> URL: https://issues.apache.org/jira/browse/PROTON-1655
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: go-binding
>Affects Versions: proton-c-0.18.0
> Environment: OSX 10.11.6, Xcode 7.3.1
>Reporter: Roddie Kieley
>Assignee: Alan Conway
>
> As discussed in [this
> comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
> when cyrus is configured for the sasl implementation the test fails due to
> the noted sasl_client_init parameter passing.
> {code}
> 11: Test command: /opt/local/bin/python
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
> "--"
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
> "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
> -I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include"
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
> roton-c"
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
> "/opt/local/bin/go" "test" "-ldflags" "-r
> /Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race"
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.02s)
> 11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
> Authentication failed [mech=PLAIN]
> {code}
> With a sasl implementation of 'none' configured we see that it attempts to
> use mech='none' and also fails:
> {code}
> 11: Test command: /opt/local/bin/python
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
> "--"
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
> "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
> -I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include"
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
> roton-c"
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
> "/opt/local/bin/go" "test" "-ldflags" "-r
> /Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race"
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.00s)
> 11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
> Authentication failed [mech=none]
> {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] [Created] (PROTON-1655) [OSX] go-test TestAuthPlain fails
Roddie Kieley created PROTON-1655:
-
Summary: [OSX] go-test TestAuthPlain fails
Key: PROTON-1655
URL: https://issues.apache.org/jira/browse/PROTON-1655
Project: Qpid Proton
Issue Type: Sub-task
Components: go-binding
Affects Versions: proton-c-0.18.0
Environment: OSX 10.11.6, Xcode 7.3.1
Reporter: Roddie Kieley
Assignee: Alan Conway
As discussed in [this
comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
when cyrus is configured for the sasl implementation the test fails due to the
noted sasl_client_init parameter passing.
{code}
11: Test command: /opt/local/bin/python
"/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
"--"
"GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
"C
GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
-I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include"
"CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
roton-c"
"PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
"/opt/local/bin/go" "test" "-ldflags" "-r
/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race"
"qpid.apach
e.org/..."
.
.
.
11: === RUN TestAuthPlain
11: --- FAIL: TestAuthPlain (0.02s)
11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=PLAIN]
{code}
With a sasl implementation of 'none' configured we see that it attempts to use
mech='none' and also fails:
{code}
11: Test command: /opt/local/bin/python
"/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
"--"
"GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
"C
GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
-I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include"
"CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
roton-c"
"PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
"/opt/local/bin/go" "test" "-ldflags" "-r
/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race"
"qpid.apach
e.org/..."
.
.
.
11: === RUN TestAuthPlain
11: --- FAIL: TestAuthPlain (0.00s)
11: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=none]
{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] [Comment Edited] (PROTON-522) Apache Qpid Proton on Mac/OSX - C/Objective-C
[
https://issues.apache.org/jira/browse/PROTON-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16218540#comment-16218540
]
Roddie Kieley edited comment on PROTON-522 at 10/25/17 12:49 PM:
-
Ran into some trouble with cyrus-sasl after seeing that the go TestAuthPlain
failed for both "Unix Makefiles" and "Xcode", in this case 7.3.1. Found that
the plugins do not get loaded on OSX due to sasl_client_init(NULL) but
rectified with sasl_client_init(pni_user_password_callbacks). Tried some build
options with 2.1.26 and 2.1.27, but fell back to using the system provided
version. Either way the updated call is required and the sasl exchange takes
place ok as all mechanism plugins get loaded, however with self created sasldb
files with the correct user, fred@proton, with password xxx the plain
authentication still fails via an updated send sasl example and dispatch 0.8.0
on the other end on a Fedora 25 box.
Dropping back to setting the sasl implementation to 'none' instead of cyrus
still results in failure unfortunately:
{code}
1: --- FAIL: TestAuthPlain (0.01s)
1: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=none]
{code}
was (Author: rkieley):
Ran into some trouble with cyrus-sasl after seeing that the go TestAuthPlain
failed for both "Unix Makefiles" and "Xcode", in this case 7.3.1. Found that
the plugins do not get loaded on OSX due to sasl_client_init(NULL) but
rectified with sasl_client_init(pni_user_password_callbacks). Tried some build
options with 2.1.26 and 2.1.27, but fell back to using the system provided
version. Either way the updated call is required and the sasl exchange takes
place ok as all mechanism plugins get loaded, however with self created sasldb
files with the correct user, fred@proton, with password xxx the plain
authentication still fails via an update send-sasl.c example and dispatch 0.8.0
on the other end on a Fedora 25 box.
Dropping back to setting the sasl implementation to 'none' instead of cyrus
still results in failure unfortunately:
{code}
1: --- FAIL: TestAuthPlain (0.01s)
1: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=none]
{code}
> Apache Qpid Proton on Mac/OSX - C/Objective-C
> -
>
> Key: PROTON-522
> URL: https://issues.apache.org/jira/browse/PROTON-522
> Project: Qpid Proton
> Issue Type: New Feature
> Components: proton-c
>Reporter: Guy Dillen
> Labels: osx
>
> I would like using Apache Qpid Proton-C from a C or Objective-C application
> on Mac/OSX to connect as a client to Windows Azure Service Bus.
--
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-522) Apache Qpid Proton on Mac/OSX - C/Objective-C
[
https://issues.apache.org/jira/browse/PROTON-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16218540#comment-16218540
]
Roddie Kieley commented on PROTON-522:
--
Ran into some trouble with cyrus-sasl after seeing that the go TestAuthPlain
failed for both "Unix Makefiles" and "Xcode", in this case 7.3.1. Found that
the plugins do not get loaded on OSX due to sasl_client_init(NULL) but
rectified with sasl_client_init(pni_user_password_callbacks). Tried some build
options with 2.1.26 and 2.1.27, but fell back to using the system provided
version. Either way the updated call is required and the sasl exchange takes
place ok as all mechanism plugins get loaded, however with self created sasldb
files with the correct user, fred@proton, with password xxx the plain
authentication still fails via an update send-sasl.c example and dispatch 0.8.0
on the other end on a Fedora 25 box.
Dropping back to setting the sasl implementation to 'none' instead of cyrus
still results in failure unfortunately:
{code}
1: --- FAIL: TestAuthPlain (0.01s)
1: electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access:
Authentication failed [mech=none]
{code}
> Apache Qpid Proton on Mac/OSX - C/Objective-C
> -
>
> Key: PROTON-522
> URL: https://issues.apache.org/jira/browse/PROTON-522
> Project: Qpid Proton
> Issue Type: New Feature
> Components: proton-c
>Reporter: Guy Dillen
> Labels: osx
>
> I would like using Apache Qpid Proton-C from a C or Objective-C application
> on Mac/OSX to connect as a client to Windows Azure Service Bus.
--
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-522) Apache Qpid Proton on Mac/OSX - C/Objective-C
[ https://issues.apache.org/jira/browse/PROTON-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171590#comment-16171590 ] Roddie Kieley commented on PROTON-522: -- The libuv now builds and runs successfully with the updates required on my PROTON-522 [branch|https://github.com/RoddieKieley/qpid-proton/tree/PROTON-522] at github. There's also an OSX focused Travis CI [project|https://travis-ci.org/RoddieKieley/qpid-proton/branches] which is a work in progress as there are sporadic failures in go-test and c-proactor-tests that I do not see locally. Locally cmake -G "Unix Makefiles" will result in 100% test pass, with very infrequent failures in test_ipv4_ipv6 while the cmake -G "Xcode" builds but doesn't actually run all the tests yet. > Apache Qpid Proton on Mac/OSX - C/Objective-C > - > > Key: PROTON-522 > URL: https://issues.apache.org/jira/browse/PROTON-522 > Project: Qpid Proton > Issue Type: New Feature >Reporter: Guy Dillen > Labels: osx > > I would like using Apache Qpid Proton-C from a C or Objective-C application > on Mac/OSX to connect as a client to Windows Azure Service Bus. -- 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-522) Apache Qpid Proton on Mac/OSX - C/Objective-C
[
https://issues.apache.org/jira/browse/PROTON-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160147#comment-16160147
]
Roddie Kieley commented on PROTON-522:
--
In checking the latest status of master with both ccmake -G 'Unix Makefiles'
and the equivalent settings for -G 'Xcode' as below with this configuration:
{code}
BUILD_CPPON
BUILD_GO OFF
BUILD_JAVASCRIPT OFF
BUILD_TESTINGOFF
BUILD_WITH_CXX OFF
CMAKE_BUILD_TYPE RelWithDebInfo
CMAKE_INSTALL_PREFIX /usr/local
CMAKE_OSX_ARCHITECTURES x86_64
CMAKE_OSX_DEPLOYMENT_TARGET
CMAKE_OSX_SYSROOT
ENABLE_HIDE_UNEXPORTED_SYMBOLS ON
ENABLE_LINKTIME_OPTIMIZATION OFF
ENABLE_SANITIZERSOFF
ENABLE_TSAN OFF
ENABLE_UNDEFINED_ERROR OFF
ENABLE_VALGRIND OFF
ENABLE_WARNING_ERROR OFF
Libuv_INCLUDE_DIR/opt/local/include
Libuv_LIBRARY/opt/local/lib/libuv.dylib
NODE NODE-NOTFOUND
PROACTOR libuv
SASL_IMPLnone
[jira] [Commented] (DISPATCH-352) Crash with empty configuration file
[
https://issues.apache.org/jira/browse/DISPATCH-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15648736#comment-15648736
]
Roddie Kieley commented on DISPATCH-352:
Correct, this only addresses the described issue that a newly 'touch'd' empty
configuration file will not seg fault at router startup. The provided 'fix'
leaves the actual validation of the router configuration file as a 'TODO' as
per line 122 in dispatch.c.
What you suggest is no longer an empty configuration file as it does indeed
have content, but the content is not valid, and that requires proper validation
as per the TODO. Splitting hairs I agree, but the described problem is
addressed, and anything further is an expansion of the requirements of the
issue and imho should be logged as a new but related issue.
That being said if anyone can point me to the appropriate configuration
documentation I'll take a look at the validation TODO I created and will create
an associated issue to track if required.
> Crash with empty configuration file
> ---
>
> Key: DISPATCH-352
> URL: https://issues.apache.org/jira/browse/DISPATCH-352
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
> Environment: RHEL 6.8x
> Git tip at commit 87d0a406c6 "DISPATCH-339 - [From Ganesh Murthy] Properly
> handle default values for host/addr."
>Reporter: Jiri Danek
> Fix For: 0.8.0
>
> Attachments: core.7166.backtrace, core.7166.bz2
>
>
> {noformat}
> $ touch empty.conf
> $ local/sbin/qdrouterd -c empty.conf
> Thu May 26 13:34:19 2016 SERVER (info) Container Name: (null)
> Segmentation fault (core dumped)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-352) Crash with empty configuration file
[
https://issues.apache.org/jira/browse/DISPATCH-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645057#comment-15645057
]
Roddie Kieley commented on DISPATCH-352:
Thanks for pulling in the changes, will be more descriptive of the actual
changes next time around.
> Crash with empty configuration file
> ---
>
> Key: DISPATCH-352
> URL: https://issues.apache.org/jira/browse/DISPATCH-352
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
> Environment: RHEL 6.8x
> Git tip at commit 87d0a406c6 "DISPATCH-339 - [From Ganesh Murthy] Properly
> handle default values for host/addr."
>Reporter: Jiri Danek
> Fix For: 0.8.0
>
> Attachments: core.7166.backtrace, core.7166.bz2
>
>
> {noformat}
> $ touch empty.conf
> $ local/sbin/qdrouterd -c empty.conf
> Thu May 26 13:34:19 2016 SERVER (info) Container Name: (null)
> Segmentation fault (core dumped)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
