Comment 0 for bug 1845337

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