make[3]: Entering directory '/var/tmp/portage/xfce-base/xfconf-4.13.4/work/xfconf-4.13.4/tests/set-properties' make[4]: Entering directory '/var/tmp/portage/xfce-base/xfconf-4.13.4/work/xfconf-4.13.4/tests/set-properties' FAIL: t-set-string FAIL: t-set-int FAIL: t-set-uint64 FAIL: t-set-double ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop_20170828-210912 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] 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 xfce-base/xfconf [ebuild N ] xfce-base/xfconf-4.13.4 USE="-debug -perl {-test}"
Created attachment 491512 [details] emerge-info.txt
Created attachment 491514 [details] emerge-history.txt
Created attachment 491516 [details] environment
Created attachment 491518 [details] etc.portage.tbz2
Created attachment 491520 [details] logs.tbz2
Created attachment 491522 [details] temp.tbz2
Created attachment 491524 [details] tests.tbz2
Created attachment 491526 [details] xfce-base:xfconf-4.13.4:20170902-052502.log
Would you be able to scrape test-suite.log as well? It's a common thing to automake tests, so you might want to take it into consideration in your scripts.
(In reply to Michał Górny from comment #9) In the attached logs.tbz2 I do have all *.log files, or do you like to have it as a separate attachment ?
Sure, that works for me. I just didn't know where to look.
For me, 4.12.1 and 4.12.0 fail the same way. However, oddly, 4.13.3 has *no* failures for me, and 4.13.4 does *not* have this issue. So it might be some dependency to blame. Excerpting the failure for others: ======================================================== xfconf 4.13.4: tests/set-properties/test-suite.log ======================================================== # TOTAL: 7 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 7 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: t-set-string ================== ** (process:31895): CRITICAL **: Test failed: xfconf_channel_set_string(channel, test_string_property, test_string) FAIL t-set-string (exit status: 1) FAIL: t-set-int =============== ** (process:32055): CRITICAL **: Test failed: xfconf_channel_set_int(channel, test_int_property, test_int) FAIL t-set-int (exit status: 1) FAIL: t-set-uint64 ================== ** (process:32214): CRITICAL **: Test failed: xfconf_channel_set_uint64(channel, test_uint64_property, test_uint64) FAIL t-set-uint64 (exit status: 1) FAIL: t-set-double ================== ** (process:32367): CRITICAL **: Test failed: xfconf_channel_set_double(channel, test_double_property, test_double) FAIL t-set-double (exit status: 1) FAIL: t-set-arrayv ================== ** (process:32534): CRITICAL **: Test failed: xfconf_channel_set_arrayv(channel, test_array_property, arr) FAIL t-set-arrayv (exit status: 1) FAIL: t-set-boolean =================== ** (process:32688): CRITICAL **: Test failed: xfconf_channel_set_bool(channel, test_bool_property, test_bool) FAIL t-set-boolean (exit status: 1) FAIL: t-set-stringlist ====================== ** (process:377): CRITICAL **: Test failed: xfconf_channel_set_string_list(channel, test_strlist_property, test_strlist) FAIL t-set-stringlist (exit status: 1)
Created attachment 548092 [details] build.log (xfconf-4.12.1, ppc) Same here with xfconf-4.12.1 on ppc.
I ran into the same failures as listed in comment 12 with xfconf-4.13.7 when trying to install it as part of setting up Gentoo on a new laptop; when I installed version 4.12.1-r1 first, then 4.13.7 passed its tests fine.
(In reply to Jonathan Lovelace from comment #14) > I ran into the same failures as listed in comment 12 with xfconf-4.13.7 when > trying to install it as part of setting up Gentoo on a new laptop; when I > installed version 4.12.1-r1 first, then 4.13.7 passed its tests fine. I can reproduce that. I'm going to investigate more.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=193a8b642d00a499a3cd92bb794e0494446fc8c2 commit 193a8b642d00a499a3cd92bb794e0494446fc8c2 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2019-06-17 09:12:22 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2019-06-17 09:12:45 +0000 xfce-base/xfconf: Fix tests to run without xfconf installed Start D-Bus session bus with correct service file to make sure xfconf D-Bus tests can spawn and communicate with the daemon. While at it, get rid of unnecessary Xvfb. Closes: https://bugs.gentoo.org/629608 Signed-off-by: Michał Górny <mgorny@gentoo.org> xfce-base/xfconf/xfconf-4.12.1-r1.ebuild | 30 ++++++++++++++++++------------ xfce-base/xfconf/xfconf-4.13.7.ebuild | 29 ++++++++++++++++++----------- 2 files changed, 36 insertions(+), 23 deletions(-)
