Source: systemd
Version: 258.1-1
Severity: serious
Control: affects -1 + src:util-linux
Control: affects -1 + src:dracut
X-Debbugs-CC: [email protected]

Hi,

systemd upstream tests as run on ci.debian.net apparently fail with 
util-linux/2.41.2-4 dracut/108-8 (and maybe some golang thing).
>From the logs I cannot tell where the problem lies.

Please investigate.

Thanks,
Chris

Partial log snip from 
https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemd/65282984/log.gz

7690s Summary of Failures:
7690s 
7690s 37/98 systemd:integration-tests / TEST-50-DISSECT                         
                      FAIL            160.26s   exit status 1
7690s 95/98 systemd:integration-tests / TEST-86-MULTI-PROFILE-UKI               
                      FAIL             66.00s   exit status 1

...

5537s [  152.305992] TEST-50-DISSECT.sh[3561]: Job for testservice-50i.service 
failed.
5537s [  152.306275] TEST-50-DISSECT.sh[3561]: See "systemctl status 
testservice-50i.service" and "journalctl -xeu testservice-50i.service" for 
details.
5537s [  152.306561] TEST-50-DISSECT.sh[3561]: Unexpected job result 'failed' 
for unit 'testservice-50i.service', assuming server side newer than us.
5537s [  152.306864] TEST-50-DISSECT.sh[3561]: Got result failed/No medium 
found for job testservice-50i.service.
5537s [  152.307176] TEST-50-DISSECT.sh[3561]: Bus n/a: changing state RUNNING 
→ CLOSED
5537s [  152.307669] TEST-50-DISSECT.sh[490]: + echo 'Subtest 
/usr/lib/systemd/tests/testdata/units/TEST-50-DISSECT.dissect.sh failed'
5537s [  152.307971] TEST-50-DISSECT.sh[490]: Subtest 
/usr/lib/systemd/tests/testdata/units/TEST-50-DISSECT.dissect.sh failed

...

For TEST-86-MULTI-PROFILE-UKI.sh I know even less what looks interesting.

Reply via email to