Description of problem: TestBoringServerCurves from crypto/tls golang internal testsuite fails when executed separately from the other tests: [root@sheep-2 ~]# GOLANG_FIPS=1 scl enable go-toolset-1.15 -- go test crypto/tls -timeout 50m -count=1 -v -v -v -run ^TestBoringServerCurves$ === RUN TestBoringServerCurves === RUN TestBoringServerCurves/curve=29 handshake_server_test.go:55: Got error: tls: no cipher suite supported by both client and server; expected to succeed === RUN TestBoringServerCurves/curve=29/fipstls === RUN TestBoringServerCurves/curve=23 === RUN TestBoringServerCurves/curve=23/fipstls === RUN TestBoringServerCurves/curve=24 === RUN TestBoringServerCurves/curve=24/fipstls === RUN TestBoringServerCurves/curve=25 === RUN TestBoringServerCurves/curve=25/fipstls --- FAIL: TestBoringServerCurves (0.00s) --- FAIL: TestBoringServerCurves/curve=29 (0.00s) --- PASS: TestBoringServerCurves/curve=29/fipstls (0.00s) --- PASS: TestBoringServerCurves/curve=23 (0.00s) --- PASS: TestBoringServerCurves/curve=23/fipstls (0.00s) --- PASS: TestBoringServerCurves/curve=24 (0.00s) --- PASS: TestBoringServerCurves/curve=24/fipstls (0.00s) --- PASS: TestBoringServerCurves/curve=25 (0.00s) --- PASS: TestBoringServerCurves/curve=25/fipstls (0.00s) FAIL FAIL crypto/tls 0.046s FAIL [root@sheep-2 ~]# The failure is not reproducible when run with other crypto/tls Boring tests (GOLANG_FIPS=1 scl enable go-toolset-1.15 -- go test crypto/tls -timeout 50m -count=1 -v -v -v -run Boring) or with FIPS disabled (GOLANG_FIPS=0). Version-Release number of selected component (if applicable): go-toolset-1.15-1.15.13-1.el7_9 go-toolset-1.15-golang-1.15.13-1.el7_9.x86_64 RHEL-7.9-updates-20210608.0 Steps to Reproduce: 1. GOLANG_FIPS=1 scl enable go-toolset-1.15 -- go test crypto/tls -timeout 50m -count=1 -v -v -v -run ^TestBoringServerCurves$
FWIW, this is also reproducible with previous go-toolset-1.15-golang-1.15.11-1.el7_9 released on devtools-2021.2.
Also reproducible with devtools-2021.4 go-toolset-1.16-golang-1.16.4-2.el7_9.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (new packages: go-toolset-1.16), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:4638