[
https://issues.apache.org/jira/browse/PROTON-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reopened PROTON-1696:
-------------------------------------
This still seems to be a problem and actually seems to be the reason the OSX
build fails when sasl is enabled.
{noformat}
13: --- FAIL: TestAuthPlain (0.00s)
13: electron_test.go:39: (from auth_test.go:127) exec:
"SASLPASSWD_EXE-NOTFOUND": executable file not found in $PATH
13: === RUN TestAuthBadPass
13: --- FAIL: TestAuthBadPass (0.00s)
13: electron_test.go:39: (from auth_test.go:127) exec:
"SASLPASSWD_EXE-NOTFOUND": executable file not found in $PATH
13: === RUN TestAuthBadUser
13: --- FAIL: TestAuthBadUser (0.00s)
13: electron_test.go:39: (from auth_test.go:127) exec:
"SASLPASSWD_EXE-NOTFOUND": executable file not found in $PATH{noformat}
For the full log see: https://travis-ci.org/astitcher/qpid-proton/jobs/357576514
> Go test of anonymous SASL fails if it can't find saslpasswd2
> ------------------------------------------------------------
>
> Key: PROTON-1696
> URL: https://issues.apache.org/jira/browse/PROTON-1696
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
> Affects Versions: proton-c-0.18.1
> Reporter: Andrew Stitcher
> Assignee: Alan Conway
> Priority: Major
> Fix For: proton-c-0.22.0
>
>
> Even if extended SASL is not being tested. In this case it shouldn't even be
> using saslpasswd2 to create an authentication database. Anonymous by its very
> nature doesn't use an authentication db.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
