[
https://issues.apache.org/jira/browse/PROTON-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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(&t)
> 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(&t)]
> 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(&t)]
> 10: FAIL: test_ipv4_ipv6(&t) (2 errors)
> {code}
> or
> {code}
> 10: TEST: test_ipv4_ipv6(&t)
> 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(&t)]
> 10: FAIL: test_ipv4_ipv6(&t) (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<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
> options=3<RXCSUM,TXCSUM>
> inet6 ::1 prefixlen 128
> inet 127.0.0.1 netmask 0xff000000
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> nd6 options=1<PERFORMNUD>
> gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
> stf0: flags=0<> mtu 1280
> en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> options=27<RXCSUM,TXCSUM,VLAN_MTU,TSO4>
> ether d4:9a:20:0d:67:fc
> inet6 fe80::d69a:20ff:fe0d:67fc%en0 prefixlen 64 scopeid 0x4
> inet 192.168.2.4 netmask 0xffffff00 broadcast 192.168.2.255
> nd6 options=1<PERFORMNUD>
> media: autoselect (1000baseT <full-duplex,flow-control>)
> status: active
> en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
> ether f8:1e:df:f4:46:8c
> nd6 options=1<PERFORMNUD>
> media: autoselect (<unknown type>)
> status: inactive
> fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 494
> lladdr d4:9a:20:ff:fe:0d:67:fc
> nd6 options=1<PERFORMNUD>
> media: autoselect <full-duplex>
> 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
