[Privoxy-devel] Releasing 3.0.35 or 4.0?

[Roland Rosenfeld]

On Sat, 11 Jan 2025, I wrote:

> ./run-privoxy-tests.sh
> This fails with
[...]
> curl returned 52, when expecting 56
>  exit FAILED

I digged a little deeper and found out that only
acl-destination-denied and acl-ip-address-denied fail (both with "curl
returned 52, when expecting 56"), while all other tests (including
upstream-tests) succeed.
The only problem is, that I have to start every single test with
 ./run-privoxy-tests.sh -t <test>
separately, since a single failing test (like the first one
acl-destination-denied) stops the start of all other tests.

So from my point of view (on my Debian 12 system) the cts testsuite is
buildable as described in your README, only the test cases
acl-destination-denied and acl-ip-address-denied fail (which should be
fixed before the release).

As far as I can see, both failed tests expect curl exit code
       56     Failure in receiving network data.
but receive
       52     The  server  did not reply anything, which here is considered an
              error.

Since both exit codes mean, that the request failed (as expected on a
denied ACL), it maybe enough to replace 56 by 52 in these test cases.

I now also see, why this happens now and didn't happen in May 2022,
when I last tested the cts code: the acl-* tests ware added since then :-)
(and crude-parental-explicit-lyrics was replaced by redirects test).

Greetings
Roland
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.privoxy.org/pipermail/privoxy-devel/attachments/20250111/6ac638bd/attachment.bin>