Also, there are NOT thousands of packages in the same situation as
systemd. systemd is a whitelisted package which is still built on i386,
which has tests that can't be run (because we run our autopkgtests on
amd64 and apt will not allow you to switch from an amd64 systemd to an
i386 systemd
> this should be fixed in hints handling in autopkgtest-cloud
+1 - autopkgtest-cloud shouldn't even bother running i386 tests for
focal or later, or at most the default should be to skip them unless
there is some configuration to explicitly run them
> the systemd test failures on i386 are
It should definitely not be changed in the systemd source package. But
the systemd test failures on i386 are already ignored by hints a I don't
understand why this bug has been raised.
(Also the triggering of tests and blocking of migration based on results
is a function of proposed-migration,
IMO this should be fixed in hints handling in autopkgtest-cloud and not
on per package basis. Obsolete tests should not be run.
** Also affects: autopkgtest-cloud
Importance: Undecided
Status: New
** Project changed: autopkgtest-cloud => auto-package-testing
--
You received this bug
And I agree that this is super annoying - for thousands of packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1887191
Title:
autopkgtest always fail on i386 for f
5 matches
Mail list logo
