Just wanted to follow up as I was able to make some progress on this issue. While I don’t entirely understand the context, it seems that this issue is related to building on Minimal Ubuntu. The failing test cases begin to pass after `unminimize`ing the
OS in my case.

On Feb 23, 2024, at 10:36 PM, Ethan Adams <[email protected]> wrote:

Attached is failing test suite (run as a part of debuild). Please let me know if there is further information I can provide.

Ethan

<testsuite.log>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi!

On Mon, 2024-02-26 at 14:33:59 -0800, Ethan Adams wrote:

On Feb 23, 2024, at 10:36 PM, Ethan Adams <[email protected]> wrote:

Attached is failing test suite (run as a part of debuild). Please let
me know if there is further information I can provide.

<testsuite.log>

Unfortunately the mailing list never received your previous message:

<https://lists.debian.org/debian-dpkg/2024/02/threads.html>

Perhaps the attached log file is triggering some spam filters or going
over some size limit. Feel free to send it directly to me.

Just wanted to follow up as I was able to make some progress on this
issue. While I don’t entirely understand the context, it seems that
this issue is related to building on Minimal Ubuntu. The failing test
cases begin to pass after `unminimize`ing the OS in my case.

W/o the needed context, from what you say above, I'd assume the system
you are building on probably lacks some of the needed dependencies. If
so then perhaps the messages could be improved to make that more clear.
But perhaps the issue is something else, let's see from the log. :)

Thanks,
Guillem

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi!

On Mon, 2024-02-26 at 16:44:11 -0800, Ethan Adams wrote:

Thanks for getting back with me and for letting me know my previous
message didn’t make it through. Also apologies for not providing the
most helpful messages - I’m new to mailing-list etiquette in general
& don’t have much experience with this project.

No worries!

I have attached the full testsuite.log at the end of this message.

Thanks, that was very helpful. (Although the mail didn't reach the
list either this time around, but I least I got it. :)

In case there are issues, the failure summary:
## ------------- ##
## Test results. ##
## ------------- ##

ERROR: All 72 tests were run,
5 failed unexpectedly.

## ------------------------ ##
## Summary of the failures. ##
## ------------------------ ##
Failed tests:
dpkg 1.22.0 test suite: dpkg tools functional test suite test groups:

NUM: FILE-NAME:LINE TEST-GROUP-NAME
KEYWORDS

43: chdir.at:5 dpkg chdir opts
dpkg command-line chdir
44: chdir.at:5 dpkg chdir env
dpkg command-line chdir
45: chdir.at:5 dpkg chdir env+opt admindir
dpkg command-line chdir
46: chdir.at:5 dpkg chdir env+opt root
dpkg command-line chdir
47: chdir.at:5 dpkg chdir env+opt root+admindir
dpkg command-line chdir

And all failures appear to be the same issue where the version command along with chdir option(s) result in the same extraneous exclude/include filters being set:
# -*- compilation -*-
43. chdir.at:5: testing dpkg chdir opts ...
../../../src/at/chdir.at:5: DPKG_DEBUG=1 dpkg --version --root=/rootdir_opt --- - 2024-02-24 06:23:36.977118387 +0000
+++ /tmp/dpkg/dpkg-1.22.0ubuntu1/build-tree/src/at/testsuite.dir/at-groups/43/stderr 2024-02-24 06:23:36.975184012 +0000
@@ -1,2 +1,7 @@
+D000001: adding exclude filter for '/usr/share/man/*'
+D000001: adding exclude filter for '/usr/share/locale/*/LC_MESSAGES/*.mo' +D000001: adding exclude filter for '/usr/share/doc/*'
+D000001: adding include filter for '/usr/share/doc/*/copyright'
+D000001: adding include filter for '/usr/share/doc/*/changelog.*'
D000001: root=/rootdir_opt admindir=/rootdir_opt/var/lib/dpkg

stdout:
Debian 'dpkg' package management program version 1.22.0 (arm64).
This is free software; see the GNU General Public License version 2 or
later for copying conditions. There is NO warranty.
43. chdir.at:5: 43. dpkg chdir opts (chdir.at:5): FAILED (chdir.at:5)

I verified this behavior outside of the test suite context by running
the binary with these options directly. And I got as far as adding
some trace logging to verify that these calls were indeed being made
to `filter_add` although I didn’t get much further than this locally.

Ok, this is a known problem, where dpkg uses the system-wide
configuration directory under /etc, where you have fragment config
files that interfere with the test suite. I guess I could filter-out
these specifically from the test output, but I was planning on working
on being able to set arbitrary config dir for dpkg after the release
that happened yesterday, so at that point this should stop being an
issue for this and a bunch of other stuff blocked on it.

Thanks,
Guillem

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)