From: W.C.A. Wijngaards Date: Thu, 9 Jul 2026 07:52:09 +0000 (+0200) Subject: - Fix unit test for malformed svcb for test on Windows. X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=ad9b12a8636dced8f7188a8e063ddc2c36c9de84;p=thirdparty%2Funbound.git - Fix unit test for malformed svcb for test on Windows. --- diff --git a/doc/Changelog b/doc/Changelog index 15bb42477..d5276f302 100644 --- a/doc/Changelog +++ b/doc/Changelog @@ -1,6 +1,7 @@ 9 July 2026: Wouter - Merge #1383 from jdek: Fix randomness generation on macOS/iOS under chroot. + - Fix unit test for malformed svcb for test on Windows. 2 July 2026: Wouter - Merge #1087: Overload `local_data_remove` to support removing diff --git a/testdata/iter_svcb_malformed.rpl b/testdata/iter_svcb_malformed.rpl index 8ac31fd2d..e08ed8e52 100644 --- a/testdata/iter_svcb_malformed.rpl +++ b/testdata/iter_svcb_malformed.rpl @@ -151,7 +151,14 @@ REPLY QR RD RA NOERROR SECTION QUESTION www.example.com. IN HTTPS SECTION ANSWER -www.example.com. 0 IN HTTPS 1 . alpn="h2" alpn="h3" +; www.example.com. 0 IN HTTPS 1 . alpn="h2" alpn="h3" +; in unknown record format, otherwise the zonefile format reader converts +; the svcb and sorts the svcbparams, and puts them in-order. That qsort is +; not stable, on some systems(windows), and that would put the identical +; key elements in a different order. With the unknown record format this +; conversion is ommitted, and the bad svcb record with duplicate keys stays +; in the same byte format. +www.example.com. IN HTTPS \# 17 00 01 00 00 01 00 03 02 68 32 00 01 00 03 02 68 33 ENTRY_END STEP 20 QUERY