armhf passed after re-running, so I guess we can ignore it. Since the
s390x failure is fixed in -proposed I'll close the bug as invalid, I can
hint away the kernel test failure since it's clearly not a kernel issue.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received th
the armhf one is confusing, as I don't see that in 234-2ubuntu9 =/
--
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/1712865
Title:
systemd 234-2ubuntu6 ADT test failure with
ah you are testing against release.
Note that gdm3:s390x was removed from release pocket without checking
that adt tests depend on it. Hence the regression in release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd i
s390x failure was fixed in systemd 234-2ubuntu9
Im confused about the armhf failure.
Why are you testing against proposed systemd, instead of the one in the
release pocket? It makes no sense to test against -proposed systemd when
it itself is failing tests.
--
You received this bug notification
s390x failure:
autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt
pinning. Retrying with using all packages from proposed
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count
armhf failure:
==
FAIL: test_search_domains_too_long (__main__.NetworkdClientTest)
--
Traceback (most recent call last):
File "/tmp/autopkgtest.WNuNXs/build.mwP
6 matches
Mail list logo
