[ 
https://issues.apache.org/jira/browse/HTTPCORE-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013735#comment-17013735
 ] 

ASF subversion and git services commented on HTTPCORE-622:
----------------------------------------------------------

Commit 97b30f385052f520a18b66faff2af7e84247e2ce in httpcomponents-core's branch 
refs/heads/4.4.x from Michael Osipov
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-core.git;h=97b30f3 ]

HTTPCORE-622: TestJSSEProviderIntegration fails if Conscrypt JNI wrapper cannot 
be loaded


> JSSEProviderIntegrationTest fails if Conscrypt JNI wrapper cannot be loaded
> ---------------------------------------------------------------------------
>
>                 Key: HTTPCORE-622
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-622
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore
>    Affects Versions: 5.0-beta10
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 5.0-beta12
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> As described on the dev ML, run the tests on a platforms which the Conscrypt 
> JAR does not contain the JNI wrapper and see this failure:
> {noformat}
> JSSEProviderIntegrationTest.*[Conscrypt TLS v1.2] » UnsatisfiedLink
> JSSEProviderIntegrationTest.*[Conscrypt TLS v1.3] » UnsatisfiedLink
> {noformat}
> with
> {noformat}
> [ERROR] testSimpleGet[Conscrypt 
> TLSv1.2](org.apache.hc.core5.testing.nio.JSSEProviderIntegrationTest)
> Time elapsed: 0.34 s  <<< ERROR!
> java.lang.UnsatisfiedLinkError: no conscrypt_openjdk_jni-freebsd-x86 in 
> java.library.path 
> {noformat}
> Ideally, {{Assume}} would verify that the provide can be loaded before tests 
> are run.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to