PASS: test-locale-util ./build-aux/test-driver: line 107: 3283 Aborted "$@" > $log_file 2>&1 FAIL: test-copy PASS: test-verbs PASS: test-signal-util PASS: test-selinux ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop_libressl_20170914-215948 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.5.1 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv sys-auth/elogind [ebuild N ] sys-auth/elogind-234.3 USE="acl pam policykit -debug (-selinux)"
Created attachment 496278 [details] emerge-info.txt
Created attachment 496280 [details] emerge-history.txt
Created attachment 496282 [details] environment
Created attachment 496284 [details] etc.portage.tbz2
Created attachment 496286 [details] logs.tbz2
Created attachment 496288 [details] sys-auth:elogind-234.3:20170924-122641.log.bz2
Created attachment 496290 [details] temp.tbz2
CCing Sven, maybe you have an idea right away before I look into it.
(In reply to Andreas Sturmlechner from comment #8) > CCing Sven, maybe you have an idea right away before I look into it. According to the log, test-login failed, too. Both should not fail, although this result is not as telling as it were if this was systemd itself. I'll have a look tonight whether a) these tests fail on my dev machine, too, and b) if they do, why this is so.
Ok. I have tested a bit and found this out: a) test-login fails, because it uses functions that are unsupported by elogind. b) test-copy does *not* fail on master, which is elogind-v235. For a) I am currently taking a look whether said functions can be enabled without systemd slices support. I have to analyze what the function chain actually tries to accomplish, and maybe I can enable a bunch of previously unsupported API functions. For b) I'll take a look what the changes between v234 and v235 are. Maybe it is just a simple fix I can back-port. I'll set this to IN_PROGRESS, although it is an upstream bug. But as nobody has raised an issue for it, this can stay here for a couple of days, no? I hope to be able to release a new series, including elogind-235.1 until the end of the year.
thanks for your time, I guess we can disable test a) then.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1db7c7784460eb0ad23bdec0a67c9a0352f81ba6 commit 1db7c7784460eb0ad23bdec0a67c9a0352f81ba6 Author: Sven Eden <yamakuzure@gmx.net> AuthorDate: 2018-01-14 22:52:49 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-01-14 23:04:54 +0000 sys-auth/elogind: 235.1 version bump, switched to meson Tests pass. Bug: https://bugs.gentoo.org/631932 Closes: https://bugs.gentoo.org/644600 Package-Manager: Portage-2.3.19, Repoman-2.3.6 sys-auth/elogind/Manifest | 1 + sys-auth/elogind/elogind-235.1.ebuild | 125 ++++++++++++++++++++++++ sys-auth/elogind/files/elogind-235.1-docs.patch | 20 ++++ 3 files changed, 146 insertions(+)}
234.3 is no longer in tree.
