Closed kloczek closed 1 month ago
Hm... weird that it's only one test that fails. I recall you are using Fedora, right? Can you share your Fedora version and also NSS version?
nss 3.96.1. I'm using my own distribution which is relative close to fedora rawhide.
oh I know what is the problem.
/usr/bin/make -O -j48 V=1 VERBOSE=1 check
The NSS tests use a shared NSS database and some test (like this one) require a specific certs in the database. If another test is running in the same time then the database might be in a wrong state. Can you rerun without "-j48" option?
I can just have per-test nss database, the only issue is that this will slow down the tests since nss will need to create database every time. Let me think about it.
The NSS tests use a shared NSS database and some test (like this one) require a specific certs in the database. If another test is running in the same time then the database might be in a wrong state. Can you rerun without "-j48" option?
Just tested and test sute fails even with -j1
Other way .. what I can try to do in my build env to diagnose those issues? 🤔
These are completely different failures:
func=xmlSecGnuTLSSignatureVerify:file=signatures.c:line=908:obj=ecdsa-sha1:subj=gnutls_pubkey_verify_hash2:error=4:crypto library function failed:gnutls error: -217: One of the involved algorithms has insufficient security level.
GnuTLS doesn't like the algos in the tests. Probably some config somewhere.
The original NSS error is gone (as expected)
refactored tests to ensure each has a separate crypto config (e.g. NSS database) to avoid collisions
Looks like test fails in one unit.