Opened 8 years ago
Closed 8 years ago
#3719 closed defect (fixed)
Unexpected systemd testsuite failures (LFS 7.6-systemd stable)
|Reported by:||Vladimir Podobaev||Owned by:|
I'm running the systemd testsuite according instructions on this page: http://linuxfromscratch.org/lfs/view/stable-systemd/chapter06/systemd.html
2 test have failed:
FAIL: test-bus-creds ==================== Assertion 'r >= 0' failed at src/libsystemd/sd-bus/test-bus-creds.c:32, function main(). Aborting. FAIL: test-rtnl =============== got link info about lo 1 left in pipe. got reply: Success 0 left in pipe. got reply: Success got link info about lo2 got IPv6 address on ifindex 2 got IPv6 address on ifindex 1 got IPv4 address on ifindex 2 got IPv4 address on ifindex 1 Assertion 'sd_rtnl_call(rtnl, m, -1, &r) == 1' failed at src/libsystemd/sd-rtnl/test-rtnl.c:85, function test_link_get(). Aborting.
This behavior is not expected (according instructions). Are these failures expected? Or is it an issue?
Thanks. Best regards, Vladimir
Change History (6)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Krejzi, thank you for your answer! Linux From Scratch forever! :) Best regards, Vladimir
comment:3 by , 8 years ago
|Status:||new → closed|
comment:4 by , 8 years ago
|Status:||closed → reopened|
comment:5 by , 8 years ago
Lets keep it here until I get the note about failing tests into the book.
comment:6 by , 8 years ago
|Status:||reopened → closed|
Added a small clarification in r10805 that other tests besides the ones previously disabled may fail.
Note: See TracTickets for help on using tickets.
Short answer: No, it's not an issue.
Long answer: Well, the testsuite is not really designed to run in chroot, and the tests that were disabled were the ones that failed for me during the testing phrase. It's also somewhat dependant on the host system's kernel (what options are enabled and what is loaded at the time), so it can't really be all perfect.
I suppose I could change "make check" to "make -k check" and note why other tests than the ones explicitly disabled may fail on some setups. Will do that when I commit the systemd-218 upgrade I have started working on, but didn't finish just yet.