From: Willy Tarreau Date: Thu, 28 May 2026 16:44:36 +0000 (+0200) Subject: REGTESTS: quic: disable quic/ocsp_auto_update for now X-Git-Tag: v3.4.0~58 X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=40508247c6b013caf20221bafce628e9f2322887;p=thirdparty%2Fhaproxy.git REGTESTS: quic: disable quic/ocsp_auto_update for now It was made from the split of the original one into the SSL and the QUIC variant. However there's a catch: both use the same certificates which includes the OCSP URL 127.0.0.1:12345, and both need to start a server on that port. Depending on the number of parallel process and their speed, they might very well work, or totally fail due to a binding conflict and the fact that the test runs for a few seconds. Let's disable the QUIC variant for now, since the whole point of the test is to verify all the sequencing, the SSL one is greatly sufficient. Maybe a better approach can be found later. --- diff --git a/reg-tests/quic/ocsp_auto_update.vtc b/reg-tests/quic/ocsp_auto_update.vtc index d1e719e75..e42e1d3ce 100644 --- a/reg-tests/quic/ocsp_auto_update.vtc +++ b/reg-tests/quic/ocsp_auto_update.vtc @@ -1,5 +1,9 @@ -#REGTEST_TYPE=slow +#REGTEST_TYPE=broken # reg-test is around ~2.5s +# It is incompatible with ssl/ocsp_auto_update.vtc running in parallel because +# both start a server on the same port, whose URL is specified in the test +# certificates. Given that the test is essentially about testing OCSP update, +# let's just use the more generic SSL one. # broken with BoringSSL.