We only can stop caring about results on s390x in artful. That is set
the expected result to fail. Checking for the real reason is just
becoming a problem because there are just so many different ADT tasks
linked to the kernel and each test fail subtly different. Or maybe in
other words, by the nex
Because that's Ubuntu 17.10
** Changed in: lxd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748440
Title:
lxd 2.18-0ubuntu6 ADT test failure with linux 4.
I don't know if you can whitelist this somehow on your side, effectively
if LXD fails on s390x and the error is:
error: The device path doesn't exist on the host and major/minor
wasn't specified.
Then all is good and you can ignore it, it's just a test infrastructure
regression, not an actual
Stefan: This is caused by a change in the s390x test infrastructure
which no longer has a ttyS0 device and so causes this test to fail.
We've had this reported before and it's been fixed in LXD 2.21 but since
it only affects a test system at Canonical and only when running the
testsuite (normal op
Hm, why is that test running 2.18 we're at 2.21 currently. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748440
Title:
lxd 2.18-0ubuntu6 ADT test failure with linux 4.13.0-33.36
To manage notif