(test) Moves NSS interoperability tests to allowed failures #66
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.
Tests against NSS master branch do not work anymore correctly. Reported
error says:
1: SSL3[1768679856]: handle alert record
1: SSL3[1768679856] received alert, level = 2, description = 70
SSL: destroy sid: sid=0x696c27a0 cached=0
1: SSL[1768679856]: handshake gathering, rv=-1
1: SSL[1768679856]: SecureSend: returning -1 count, error -12190
tstclnt: write to SSL socket failed: SSL_ERROR_PROTOCOL_VERSION_ALERT: Peer reports incompatible or unsupported protocol version.
Not sure what's the root cause of the problem, but as the last commit on
tls-tris has succeeded, the problem/change causing regression must be on
NSS side.
I propose to temporarily allow failures of those tests to keep tls-tris build
regression less.