3.0.34-3ubuntu1 autopkgtest failure

[Chris Peterson]

autopkgtests are failing on all architectures due to a failing curl command:

https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/armhf/p/privoxy/20240326_221527_50316@/log.gz

273s 2024-03-26 22:11:01: Skipping test 709: depends on config line matching: 'enable-edit-actions\s+1'.
273s 2024-03-26 22:11:01: Skipping test 744: depends on 'FEATURE_HTTPS_INSPECTION' being set to 'No'.
274s 2024-03-26 22:11:02: Fetch failure: 'curl: (52) Empty reply from server'
274s 2024-03-26 22:11:02: Fetch failure: 'curl: (7) Failed to connect to 127.0.0.1 port 8119 after 0 ms: Couldn't connect to server'
274s 2024-03-26 22:11:02: Oh noes. Running curl failed 1 times in a row. Last error: 'curl: (7) Failed to connect to 127.0.0.1 port 8119 after 0 ms: Couldn't connect to server'. Fatal error. Exiting.
274s #### pass 2 with some more options enabled
274s 2024-03-26 22:11:02: Asking Privoxy for the number of action files available ...
274s 2024-03-26 22:11:02: Fetch failure: 'curl: (7) Failed to connect to 127.0.0.1 port 8119 after 0 ms: Couldn't connect to server'
274s /tmp/autopkgtest.E1vA3h/build.TxZ/src/debian/tests/privoxy-regression-test: 61: kill: No such process
274s
274s 2024-03-26 22:11:02: Fetch failure: 'curl: (7) Failed to connect to 127.0.0.1 port 8119 after 0 ms: Couldn't connect to server'
274s 2024-03-26 22:11:02: Oh noes. Running curl failed 1 times in a row. Last error: 'curl: (7) Failed to connect to 127.0.0.1 port 8119 after 0 ms: Couldn't connect to server'. Fatal error. Exiting.
274s Stopping privoxy on port 8119
274s autopkgtest [22:11:02]: test privoxy-regression-test: -----------------------]
278s autopkgtest [22:11:06]: test privoxy-regression-test: - - - - - - - - - - results - - - - - - - - - -
278s privoxy-regression-test FAIL non-zero exit status 1
278s autopkgtest [22:11:06]: test privoxy-regression-test: - - - - - - - - - - stderr - - - - - - - - - -
278s /tmp/autopkgtest.E1vA3h/build.TxZ/src/debian/tests/privoxy-regression-test: 61: kill: No such process
278s

[Roland Rosenfeld (roland)]

At the moment I don't have an idea, what's going wrong in the Ubuntu autopkgtest here.
But it looks as privoxy does not listen on 8119 as expected but fails and dies (the message, that privoxy cannot be killed because there is no such process in line 61 of privoxy-regression-test also leads to this conclusion).

Sadly we currently have too less information here. I just committed two patches to the Debian repository https://salsa.debian.org/debian/privoxy, that should extend logging of privoxy testsuite and preserve the logfiles into artifacts.

Maybe this helps to track this issue down. I plan to release this as privoxy 3.0.34-4 when the 64bit time_t migration is completed, so this may take some weeks.

In the meantime you can try out the attached patch.

[Roland Rosenfeld (roland)]

At the moment I don't have an idea, what's going wrong in the Ubuntu autopkgtest here.
But it looks as privoxy does not listen on 8119 as expected but fails and dies (the message, that privoxy cannot be killed because there is no such process in line 61 of privoxy-regression-test also leads to this conclusion).

Sadly we currently have too less information here. I just committed two patches to the Debian repository https://salsa.debian.org/debian/privoxy, that should extend logging of privoxy testsuite and preserve the logfiles into artifacts.

Maybe this helps to track this issue down. I plan to release this as privoxy 3.0.34-4 when the 64bit time_t migration is completed, so this may take some weeks.

In the meantime you can try out the attached patch.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "artifacts-log.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]