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
When running tlsfuzzer within NSS upstream CI, the following test gets timeout:
test-tls13-version-negotiation.py:stdout:SSL 2.0 ClientHello with TLS 1.3 version and TLS 1.3 only ciphersuites ...
test-tls13-version-negotiation.py:stdout:Error encountered while processing node <tlsfuzzer.expect.ExpectAlert object at 0x7f00e9857b50> (child: None) with last message being: None
test-tls13-version-negotiation.py:stdout:Error while processing
test-tls13-version-negotiation.py:stdout:Traceback (most recent call last):
test-tls13-version-negotiation.py:stdout: File "scripts/test-tls13-version-negotiation.py", line 435, in main
test-tls13-version-negotiation.py:stdout: runner.run()
test-tls13-version-negotiation.py:stdout: File "/home/dueno/devel/tests_results/security/localhost.1/tlsfuzzer/tlsfuzzer/tlsfuzzer/runner.py", line 200, in run
test-tls13-version-negotiation.py:stdout: "Timeout when waiting for peer message")
test-tls13-version-negotiation.py:stdout:AssertionError: Timeout when waiting for peer message
Describe how to reproduce the problem
apply the patch from the phabricator to nss trunk
build nss
modify the tlslite-ng commit ID in tests/tlsfuzzer/tlsfuzzer.sh
run the tests
Expected behaviour
The test receives the appropriate alert (decode_error).
The text was updated successfully, but these errors were encountered:
Bug Report
System Information
Problem description
When running tlsfuzzer within NSS upstream CI, the following test gets timeout:
Describe how to reproduce the problem
Expected behaviour
The test receives the appropriate alert (decode_error).
The text was updated successfully, but these errors were encountered: