New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes MAISTRA-2202 updated expired certs #80
Conversation
- test/config/integration/certs - test/extensions/transport_sockets/tls/test_data also a small change in test/integration/integration_test.cc to get ResponseFramedByConnectionCloseWithReadLimits passing. TestDelayedConnectionTeardownTimeoutTrigger can be flaky due to delayed close repeatedly firing too early.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left one question for consideration, but LGTM
@dmitri-d: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
2 similar comments
@dmitri-d: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@dmitri-d: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
- test/config/integration/certs - test/extensions/transport_sockets/tls/test_data also a small change in test/integration/integration_test.cc to get ResponseFramedByConnectionCloseWithReadLimits passing. TestDelayedConnectionTeardownTimeoutTrigger can be flaky due to delayed close repeatedly firing too early.
also a small change in test/integration/integration_test.cc to get
ResponseFramedByConnectionCloseWithReadLimits passing.
TestDelayedConnectionTeardownTimeoutTrigger can be flaky due to delayed
close repeatedly firing too early.