Andreas Tille wrote: > > Unfortunately the autopkgtest in my local pbuilder I get:
Just out of curiosity, how do you run autopkgtests in pbuilder? I couldn't find any documentation about it. > However, some tests are failing for i386. I decided to remove the > package from all 32bit architectures to reduce the maintenance burden. > I'm fine if someone might have a better idea to solve this problem. I think this is way too drastic and such approach should be used as a last resort (ideally coordinated with upstream as well). Only 2 test files out of 310 fail which indicates that the package is far from broken on i386 (cmdlineparseroutput is flaky and should be always disabled). I suggest to skip 2dimage-cost-lsd and 3d-vectorfield tests on 32-bit architectures for the time being, at least until someone with better C++ knowledge investigates the real culprit. > We also need to deactivate dh_auto_test for architecture=all builds > (which I did not do yet). Right; I'll do this. I'll also remove the SALSA_BUILD stuff as apparently it's not needed. > As you can see here > > https://salsa.debian.org/med-team/mia/-/pipelines/959946 > > some work is left. The i386 build should have vanished (see above) but > we need to deal with the other issues (probably ignoring reprotest is > fine). The autopkgtest and reprotest tests failed due to a libtool bug (#1118477) which has been fixed in the meantime. The piuparts test fails for me locally too because the binary packages in the archive (from -13) are not installable (they depend on old library packages that are no longer available). I think (but I'm not sure) that when britney schedules this test, the inevitable failure will not be a blocker for the migration of the package to testing.
