[
https://issues.apache.org/jira/browse/PROTON-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16212665#comment-16212665
]
ASF subversion and git services commented on PROTON-1639:
---------------------------------------------------------
Commit e479d4c0c65c8fe7aec60f6b34416c70d99e93fc in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=e479d4c ]
PROTON-1639: epoll.c assert() on immediate connect() failure
The epoll proactor was asserting if a connect() call failed immediately.
This doesn't show up in most tests because the connect() is non-blocking, and
most failures are deferred to epoll and handled correctly
However trying to connect() to an IPv6 address with IPv6 disabled does fail
immediately and causes an assert() failure.
> proton.c ipv6 test does not detect lack of ipv6 support
> -------------------------------------------------------
>
> Key: PROTON-1639
> URL: https://issues.apache.org/jira/browse/PROTON-1639
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.17.0
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: proton-c-0.18.0
>
>
> This test tries to listen on the ipv6 "::" undefined address, and expects
> that to fail if ipv6 is not supported, in which case it skips the remaining
> ipv6 tests. However this has been broken at some point as the listen attempt
> claims to succeed even if ipv6 has been disabled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
