Looks like another "guess what strange thing the buildd is doing this time" problem. The failing test is (effectively) pmap -XX $pid $pid | grep KB
And make sure the first numbers of each row are the same. Because it is the same process, it should be the same. There is the same test for pmap -X and that passed. The test works every time I have tried, on any system I have tried, so the buildd is doing something odd, but without anything else to go on that's going to be impossible to fix. I'm going to adjust the error messages to see which match is failing, but that's only in the upstream package at the moment. - Craig On Sat, 16 Sept 2023 at 20:57, Sebastian Ramacher <sramac...@debian.org> wrote: > Source: procps > Version: 2:4.0.4-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the > past) > X-Debbugs-Cc: sramac...@debian.org > > > https://buildd.debian.org/status/fetch.php?pkg=procps&arch=amd64&ver=2%3A4.0.4-1&stamp=1694089907&raw=0 > > WARNING: Couldn't find tool init file > Test run by buildd on Thu Sep 7 12:31:32 2023 > Native configuration is x86_64-pc-linux-gnu > > === pmap tests === > > Schedule of variations: > unix > > Running target unix > Using /usr/share/dejagnu/baseboards/unix.exp as board description file for > target. > Using /usr/share/dejagnu/config/unix.exp as generic interface file for > target. > Using /<<PKGBUILDDIR>>/testsuite/config/unix.exp as > tool-and-target-specific interface file. > Running /<<PKGBUILDDIR>>/testsuite/pmap.test/pmap.exp ... > FAIL: pmap XX pid pid has same total > > === pmap Summary === > > # of expected passes 13 > # of unexpected failures 1 > /<<PKGBUILDDIR>>/src/pmap version 4.0.4 > > WARNING: Couldn't find tool init file > Test run by buildd on Thu Sep 7 12:31:32 2023 > Native configuration is x86_64-pc-linux-gnu > > > Cheers > -- > Sebastian Ramacher >
