You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did some investigation and the test is not failing due to client being able to authenticate and proceed successfully but due to Exception caught not being of SSLException type but SocketException ( Broken pipe ) where startSSLHandshake function is somewhere in the middle of the exception stack trace. This way we catch it the general Exception catch block and throw AssertionError failing the test.
I suspect the handshake implementation changed between versions so that server suddenly closes it's resources at some point and causes the client to read/write to a closed connection which tends to throw previously mentioned "Broken pipe" exception.
I propose just including the SocketException as the possible cause of the auth fail assertions as the initialization of the server and the rest of the SSL setup seem standard to me.
What is the bug?
Failing PerformanceAnalyzerWebServerTest.testUnauthenticatedClientGetsRejected for Java17
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: