The 'good' tests have a dir being mounted '/dev/.lxd-mounts' while the 'bad'
tests have a dir being mounted '/dev/.lxc' as well as '/dev/.lxc/proc'. In the
'bad' case, the test is making sure there are no unexpected writable
directories other than the single one it's expecting (and other expected ones
which are ignored, e.g. /tmp, /var/tmp, ...), and it's finding a writable dir
under /dev/.lxc/ that it of course wasn't expecting:
+ test
/dev/.lxc/proc/1079/fd/dev/.lxc/proc/1079/map_files/dev/.lxc/proc/1079/task/1079/fd/var/lib/private/quux/pief/var/lib/private/waldo
= /var/lib/private/quux/pief/var/lib/private/waldo
something (maybe lxc itself?) seems to be mounting /proc under the
/dev/.lxc dir, or something like that...when using lxd, that problem
doesn't seem to happen. I'd be inclined to blame lxc for this, not the
test itself.
Did the armhf testbeds get changed from lxd to lxc recently?
--
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/1845337
Title:
Disco autopkgtest @ armhf fails root-unittests -> test-execute ->
exec-dynamicuser-statedir.service
Status in qemu package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in qemu source package in Disco:
New
Status in systemd source package in Disco:
New
Bug description:
Since the recent few weeks systemd autopkgtest @ armhf @ disco fail
[1].
The log is very (very) long and partially interwoven due to concurrent
execution.
Somewhere in between we see this subcase is the one failing: root-unittests
Of this test (which again has many subtests) it is: test-execute
And of this again it is (always):
I'll attach bad and good case full and stripped logs.
The diff of those comes down to just:
1. execute a find in a shell
2. shell exits
3. exec-dynamicuser-statedir.service: Main process exited, code=exited,
status=0/SUCCESS
vs
3. exec-dynamicuser-statedir.service: Main process exited, code=exited,
status=1/FAILURE
4. in the bad case that triggers an assertion
The find that fails is:
find / -path /var/tmp -o -path /tmp -o -path /proc -o -path
/dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf
Good and bad case are the same most recent version
systemd/240-6ubuntu5.7.
Maybe something is bad in the containers we have for armhf in regard to these
paths?
Was there any change we'd know of?
If there is nothing known, could we force-badtest it to get it out of
the way of ongoing migrations?
[1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
