From: Nicki Křížek <nicki@isc.org>
Date: Fri, 21 Nov 2025 13:35:57 +0000 (+0100)
Subject: Set stricter respdiff:recent-named threshold
X-Git-Tag: v9.21.16~32^2~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=92ae68764954b3606a899f5f3ecd16846cda7324;p=thirdparty%2Fbind9.git

Set stricter respdiff:recent-named threshold

This job is testing the current BIND implementation against the latest
released version. Unless there has been a behaviour change, there should
be no difference.

In practice, there is a small number of differences caused by upstream
discrepencies. Some of those cause "upstream unstable" answers which are
excluded from the results, but statistically, some of those will end up
being detected as differences on the resolver under test.

Currently, there seems to be about 300 upstream unstable answers with
typically around 50-60 differences. Setting the threshold to 0.1 should
be stable enough to pass if there are no changes, yet sensitive enough
to detect even fairly small changes to behaviour.
---

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 90b2b9d8348..196ce3f807a 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -2027,7 +2027,7 @@ respdiff:recent-named:
     CC: gcc
     CFLAGS: "${CFLAGS_COMMON} -DISC_TRACK_PTHREADS_OBJECTS"
     EXTRA_CONFIGURE: "-Doptimization=g"
-    MAX_DISAGREEMENTS_PERCENTAGE: "0.3"
+    MAX_DISAGREEMENTS_PERCENTAGE: "0.1"
 
 # Performance tests