node icon indicating copy to clipboard operation
node copied to clipboard

Test failures with OpenSSL 3.2.2

Open richardlau opened this issue 8 months ago • 6 comments

A number of Node.js tests fail when Node.js is compiled dynamically linked against OpenSSL 3.2 (tested with OpenSSL 3.2.2). i.e.

./configure --shared-openssl
make -j 4 test-ci

Full tap results: https://gist.github.com/richardlau/ce642daf2ffd581755232a924f9f8f63

Failures:

  • [x] out/Release/node /home/nodejs/node/test/parallel/test-crypto-dh.js https://github.com/nodejs/node/pull/53503
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-http2-https-fallback.js Also fails with OpenSSL 3.0.14 https://github.com/nodejs/node/pull/53373
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-http2-server-unknown-protocol.js Also fails with OpenSSL 3.0.14 https://github.com/nodejs/node/pull/53373
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-https-client-checkServerIdentity.js https://github.com/nodejs/node/pull/54599
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-https-strict.js https://github.com/nodejs/node/pull/54599
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-alert-handling.js https://github.com/nodejs/node/pull/54909
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-cert-regression.js https://github.com/nodejs/node/pull/54968
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-client-getephemeralkeyinfo.js https://github.com/nodejs/node/pull/55030
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-alpn-server-client.js Also fails with OpenSSL 3.0.14 https://github.com/nodejs/node/pull/53373
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-client-mindhsize.js https://github.com/nodejs/node/pull/54739
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-client-renegotiation-13.js https://github.com/nodejs/node/pull/54599
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-client-auth.js https://github.com/nodejs/node/pull/54610
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-client-verify.js https://github.com/nodejs/node/pull/54599
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-empty-sni-context.js https://github.com/nodejs/node/pull/53384
  • [x] out/Release/node --no-warnings /home/nodejs/node/test/parallel/test-tls-dhe.js https://github.com/nodejs/node/pull/54903
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-getcipher.js https://github.com/nodejs/node/pull/54972
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-junk-server.js https://github.com/nodejs/node/pull/54926
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-multiple-cas-as-string.js https://github.com/nodejs/node/pull/54599
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-peer-certificate-encoding.js https://github.com/nodejs/node/pull/54599
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-multi-key.js https://github.com/nodejs/node/pull/54599
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-psk-circuit.js https://github.com/nodejs/node/pull/53384
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-sni-server-client.js https://github.com/nodejs/node/pull/54599
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-set-ciphers.js https://github.com/nodejs/node/pull/55016
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-sni-option.js https://github.com/nodejs/node/pull/54599
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-server-verify.js https://github.com/nodejs/node/pull/54599
  • [x] out/Release/node /home/nodejs/node/test/parallel/test-tls-junk-closes-server.js also reported in https://github.com/nodejs/node/issues/52482 https://github.com/nodejs/node/pull/55089#top

In our Jenkins CI we currently test in node-test-commit-linux-containered Node.js dynamically linked against OpenSSL 3.0 and 3.1. Addressing the above test failures would be required before we can add testing against OpenSSL 3.2 to the CI.

richardlau avatar Jun 07 '24 15:06 richardlau