[
https://issues.apache.org/jira/browse/HADOOP-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18037419#comment-18037419
]
ASF GitHub Bot commented on HADOOP-19719:
-----------------------------------------
steveloughran opened a new pull request, #8075:
URL: https://github.com/apache/hadoop/pull/8075
Downgrade to a skipped tests if the OS doesn't have GLIBC_2.34.
The branch-3.4 version of the patch doesn't delete testJSEENoGCMJava8() and
uses classic junit assumeTrue() calls.
### How was this patch tested?
Yetus needs to do this
### For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Upgrade to wildfly version with support for openssl 3
> -----------------------------------------------------
>
> Key: HADOOP-19719
> URL: https://issues.apache.org/jira/browse/HADOOP-19719
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, fs/azure, fs/s3
> Affects Versions: 3.5.0, 3.4.2
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0, 3.4.3
>
>
> Wildfly 2.1.4
> * doesn't work with openssl 3 (that symbol change...why did they do that?)
> we need a version with
> https://github.com/wildfly-security/wildfly-openssl-natives/commit/6cecd42a254cd78585fefd9a0e41ad7954ece80d
> 2.2.5.Final does the openssl 3 support.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
