Update tlsfuzzer in CI and enable more tests
Categories
(NSS :: Test, task, P3)
Tracking
(Not tracked)
People
(Reporter: ueno, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [nss-fx][nss-ci][nss-tests])
Attachments
(1 file)
The tlsfuzzer module used in the CI hasn't been updated since Sept 2019, and only a subset of TLS 1.3 tests (+ tests that cover specific bugs) are enabled. On the other hand, in tlsfuzzer several improvements were added to the harness to make the CI integration easier:
https://tlsfuzzer.readthedocs.io/en/latest/ci-integration.html
It would be good to review the current integration and enable more tests.
Updated•5 years ago
|
Comment 1•4 years ago
|
||
We recently updated tlsfuzzer so that we could enable a test for Bug 1662515.
Since that update we've been seeing intermittent failures for
tlsfuzzer/test-tls13-signature-algorithms.py, which is a bit surprising as
our config labels this test as "exp_pass: false". This patch aligns our
selfserv configuration for the tls13-sig-algs test with the requirements of
the test, and should fix the issue, but there are clearly some other
underlying problems here.
Comment 2•1 year ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.
For more information, please visit BugBot documentation.
Comment 3•1 year ago
|
||
Fixed by the changeset below?
https://hg.mozilla.org/projects/nss/rev/7e7070e56bf7a3937cd9338a52573c896af07e3f
Description
•