Source: privoxy Version: 4.2.0-1 Severity: normal Dear Maintainer,
The privoxy check-ssl autopkgtest is flaky and unreliable. It utilises badssl.com which regularly returns 503 or other error instead of the expected 403. 62s 2026-06-26 09:08:52: Requesting https://expired.badssl.com/ 62s 2026-06-26 09:08:52: Ooops. We expected status code 403, but received: 503. This breaks privoxy's autopkgests and (perhaps more importantly) introduces apparent regressions in other packages. The Github source for badssl.com[1] makes it clear that baddssl.com is not suitable for automated CI testing. Please remove the test, or at least mark it flaky until it can provide the necessary reliability and coverage. Thanks. Mark [1] https://github.com/chromium/badssl.com#disclaimer -- System Information: Debian Release: forky/sid Architecture: amd64 (x86_64) Kernel: Linux 6.19.11+deb14-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: OpenRC (via /run/openrc), PID 1: init
