Assertion 'streq(formatted, "ONE TWO THREE\n" "xxx yyy yes\n" "a long field yyy no\n")' failed at ../elogind-241.3/src/test/test-format-table.c:65, function main(). Aborting. 118/177 test-format-table FAIL 0.01 s (killed by signal 6 SIGABRT) /* test_align_power2 */ /* test_max */ /* test_container_of */ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-desktop-gnome_libressl-abi32+64-test_20190621-191902 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) emerge -qpvO sys-auth/elogind [ebuild N ] sys-auth/elogind-241.3 USE="acl pam policykit -debug -doc (-selinux)"
Created attachment 580494 [details] emerge-info.txt
Created attachment 580496 [details] emerge-history.txt
Created attachment 580498 [details] environment
Created attachment 580500 [details] etc.portage.tbz2
Created attachment 580502 [details] logs.tbz2
Created attachment 580504 [details] sys-auth:elogind-241.3:20190622-211624.log.bz2
Created attachment 580506 [details] temp.tbz2
Happens on ia64 as well (when I was attempting to stabilize)
On inspection, it's a test ensuring some table printing code works. Not a stabilization blocker IMO.
happens on sparc, too.
Interestingly, reproducible on amd64 now too when it seemed to work in the past.
Sorry for the late reply. This should be fixed in the next release, which will be somewhere in the next week.
(In reply to Sven Eden from comment #12) > Sorry for the late reply. > > This should be fixed in the next release, which will be somewhere in the > next week. unfortunately I have to eat my words. I had vacation the previous two weeks, and everything should have been done, tested and finished by now. Easy enough on holidays. But family had other plans and kept me so busy, that I accomplished nothing. :-( Sorry for the delay!
Could you please try with latest commit, please? There is a sys-auth/elogind-241.9999 live ebuild in my seden overlay via layman. If the test still fails, I'd like to see the file build/meson-logs/testlog.txt Unfortunately the printing of the failed table didn't make it into the uploaded sys-auth:elogind-241.3:20190622-211624.log --- Note: The only way this can possibly fail is, if the tinderbox somehow reports a size of less than 50 columns. Is that box this small?
(In reply to Sven Eden from comment #14) > Note: The only way this can possibly fail is, if the tinderbox somehow > reports a size of less than 50 columns. Is that box this small? it has 6 cores/12 threads and 128 GB of RAM, that should work.
with 241.9999: > 118/177 test-format-table OK 0.02 s overall: > Ok: 174 > Expected Fail: 0 > Fail: 0 > Unexpected Pass: 0 > Skipped: 3 > Timeout: 0
(In reply to Andreas Sturmlechner from comment #16) > with 241.9999: > > > 118/177 test-format-table OK 0.02 s > > overall: > > > Ok: 174 > > Expected Fail: 0 > > Fail: 0 > > Unexpected Pass: 0 > > Skipped: 3 > > Timeout: 0 *yay* I am still testing prior releasing the new version. I had some weird behavior after waking from hibernation, but that could have come with doing lots of package updates and kernel changes. Hopefully I can release the new version sometime tomorrow, as I am also working on v243, which has some nice new additions, like supporting booting into firmware (aka EFI support).
elogind v241.4 has been released. Sorry that it took so long, but waking up from hibernate crashes the kernel on my machine, and I wanted to investigate that first. It appears to be a problem with kernel-5.3.x on my machine alone. Haven't had any report from elsewhere, and everything is fine with kernel-5.2.x. *shrug* There hasn't been any changes to the hibernation code anyway...
