add support for centos8 to autest #7268
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
masaori335
pushed a commit
to masaori335/trafficserver
that referenced
this pull request
Mar 31, 2021
masaori335
pushed a commit
to masaori335/trafficserver
that referenced
this pull request
Mar 31, 2021
* asf/8.1.x: Fix truncated reponse on HTTP/2 graceful shutdown (apache#7267) Updated ChangeLog Updated ChangeLog Update HttpTransact.cc add support for centos8 (apache#7268)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The autest bootstrap.py will not currently work with centos8
This adds some changes for centos8 usage. It defines a centos8 specific install section since the rh-python package no longer exists and is included as python3. Along with that it removes the enabling of the
/optinstalls of python3.Finally it sets the crypto policies to match the centos7 policy which is now considered 'legacy'. This needs to be done for tests that rely on tls1.0 support to exist and be allowed otherwise those tests will fail because curl cannot set a specific tls version below 1.2.