We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This test occasionally fails due to the lack of an exception expected to be thrown from the test client using the incorrect credentials.
However looking at the test client logs the ssl negotiation failed as expected, but apparently the exception does not get thrown.
The exception fails to be thrown by client FooRx3 here
But if we see the output logs from FooRx3 we can see that the ssl handshake did fail as expected:
root:system_test.py:2046 2024-11-25 21:01:50.557039 AsyncTestReceiver FooRx3: AsyncTestReceiver Starting reactor proton:_reactor.py:1052 Connecting to Url('amqps://localhost:22445')... root:system_test.py:2046 2024-11-25 21:01:50.571349 AsyncTestReceiver FooRx3: AsyncTestReceiver on_transport_error=SSL Failure: error:0A000086:SSL routines::certificate verify failed root:system_test.py:2046 2024-11-25 21:01:50.571529 AsyncTestReceiver FooRx3: Disconnected proton:_reactor.py:1104 Disconnected, already closed root:system_test.py:2046 2024-11-25 21:01:50.572501 AsyncTestReceiver FooRx3: AsyncTestReceiver reactor thread done
Notice the expected certificate verify failed in the above, yet no exception was generated.
The text was updated successfully, but these errors were encountered:
Issue skupperproject#1683: Enable verbose logging in AsyncTestReceiver
6969b68
This does not fix the issue but will give more detail should the error happen again.
Issue #1683: Enable verbose logging in AsyncTestReceiver (#1684)
ed3f3fa
Patch does not fix the issue: just adds more debug info in case it occurs again
Sorry, something went wrong.
kgiusti
Successfully merging a pull request may close this issue.
This test occasionally fails due to the lack of an exception expected to be thrown from the test client using the incorrect credentials.
However looking at the test client logs the ssl negotiation failed as expected, but apparently the exception does not get thrown.
The exception fails to be thrown by client FooRx3 here
But if we see the output logs from FooRx3 we can see that the ssl handshake did fail as expected:
Notice the expected certificate verify failed in the above, yet no exception was generated.
The text was updated successfully, but these errors were encountered: