After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 768799 - >=dconf-0.16.1 fails on test
>=dconf-0.16.1 fails on test
Product: dconf
Classification: Core
Component: dconf
Other Linux
: Normal normal
: ---
Assigned To: dconf-maint
Depends on:
Reported: 2016-07-14 09:56 UTC by Émeric MASCHINO
Modified: 2018-09-21 16:17 UTC
See Also:
GNOME target: ---
GNOME version: ---

dconf-0.26.0 build.log (36.94 KB, text/plain)
2016-07-14 09:56 UTC, Émeric MASCHINO
dconf-0.26.0 gsettings/test-suite.log (308 bytes, text/plain)
2016-07-14 09:57 UTC, Émeric MASCHINO

Description Émeric MASCHINO 2016-07-14 09:56:48 UTC
Created attachment 331471 [details]
dconf-0.26.0 build.log


I was asked by Gentoo team to report this issue.

While stabilizing dconf on Gentoo, it appears that dconf failed to pass test. No problem when tests are disabled.

Unfortunately, gsettings/test-suite.log is not that verbose and simply says:

   dconf 0.16.1: gsettings/test-suite.log

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2


Same things happen with current dconf-0.26.0 (build.log and test-suite.log attached).

Let me know how I can help further.


Comment 1 Émeric MASCHINO 2016-07-14 09:57:52 UTC
Created attachment 331473 [details]
dconf-0.26.0 gsettings/test-suite.log
Comment 2 Allison Karlitskaya (desrt) 2016-07-30 19:49:32 UTC
Are you on an exotic platform of some kind?  I notice you selected "Hardware: Other".
Comment 3 Allison Karlitskaya (desrt) 2016-07-30 19:49:44 UTC
Are you on an exotic platform of some kind?  I notice you selected "Hardware: Other".
Comment 4 Émeric MASCHINO 2016-08-02 07:18:43 UTC
(In reply to Allison Lortie (desrt) from comment #3)
> Are you on an exotic platform of some kind?  I notice you selected
> "Hardware: Other".

Itanium CPU here. More specifically, Gentoo Linux ia64 it does matter.

Comment 5 Gilles Dartiguelongue 2016-09-30 18:13:31 UTC
Could you run:
$ nm --dynamic --defined-only /var/tmp/portage/gnome-base/dconf-0.26.0/work/dconf-0.26.0/gsettings/ so we can see what extra symbol is causing the failure maybe ?
Comment 6 Émeric MASCHINO 2016-10-03 12:11:01 UTC
(In reply to Gilles Dartiguelongue from comment #5)
> Could you run:
> $ nm --dynamic --defined-only
> /var/tmp/portage/gnome-base/dconf-0.26.0/work/dconf-0.26.0/gsettings/
> so we can see what extra symbol is causing the failure
> maybe ?

Sure. Here's the output:

00000000000263d8 S __bss_start
000000000000fa00 t dconf_changeset_string_ptr_compare
0000000000008140 t dconf_engine_change_completed
0000000000007c40 t dconf_engine_is_writable_changeset_predicate
0000000000006e40 t dconf_engine_ref
000000000000bfc0 t dconf_engine_source_file_finalize
000000000000bf40 t dconf_engine_source_file_init
000000000000bf80 t dconf_engine_source_file_needs_reopen
000000000000c000 t dconf_engine_source_file_reopen
000000000000c480 t dconf_engine_source_service_finalize
000000000000c880 t dconf_engine_source_service_init
000000000000c7c0 t dconf_engine_source_service_needs_reopen
000000000000c4c0 t dconf_engine_source_service_reopen
000000000000c940 t dconf_engine_source_system_finalize
000000000000cc40 t dconf_engine_source_system_init
000000000000cb80 t dconf_engine_source_system_needs_reopen
000000000000c980 t dconf_engine_source_system_reopen
000000000000c280 t dconf_engine_source_user_finalize
000000000000c3c0 t dconf_engine_source_user_init
000000000000c200 t dconf_engine_source_user_needs_reopen
000000000000c2c0 t dconf_engine_source_user_reopen
0000000000008500 t dconf_engine_watch_established
000000000000ec80 t dconf_gdbus_method_call
000000000000e780 t dconf_gdbus_method_call_done
000000000000ef40 t dconf_gdbus_signal_handler
000000000000eec0 t dconf_gdbus_summon_bus
000000000000f080 t dconf_gdbus_worker_thread
0000000000006240 t dconf_settings_backend_add_to_changeset
0000000000005e80 t dconf_settings_backend_class_intern_init
00000000000064c0 t dconf_settings_backend_finalize
0000000000005e00 t dconf_settings_backend_free_weak_ref
0000000000006200 t dconf_settings_backend_get_writable
0000000000005d40 t dconf_settings_backend_init
0000000000006440 t dconf_settings_backend_read
00000000000063c0 t dconf_settings_backend_read_user_value
0000000000006380 t dconf_settings_backend_reset
00000000000061c0 t dconf_settings_backend_subscribe
0000000000006140 t dconf_settings_backend_sync
0000000000006180 t dconf_settings_backend_unsubscribe
00000000000062c0 t dconf_settings_backend_write
0000000000006580 t dconf_settings_backend_write_tree
0000000000013320 t __do_global_ctors_aux
0000000000005c00 t __do_global_dtors_aux
0000000000005cc0 t __do_jv_register_classes
00000000000263d8 G _edata
0000000000026478 B _end
00000000000133a0 T _fini
0000000000006680 T g_io_module_load
0000000000006900 T g_io_module_query
0000000000006880 T g_io_module_unload
0000000000005b80 t gmon_initializer
0000000000003d70 T _init
000000000000f680 t unref_gvariant0

Anything obvious?

Comment 7 Gilles Dartiguelongue 2016-10-07 07:43:19 UTC
Yup, on my amd64 installation (from builddir):

# nm --dynamic --defined-only ./gsettings/
000000000020e008 B __bss_start
000000000020e008 D _edata
000000000020e0f8 B _end
000000000000a1a4 T _fini
0000000000003dc0 T g_io_module_load
0000000000003f10 T g_io_module_query
0000000000003ec0 T g_io_module_unload
0000000000003180 T _init
Comment 8 GNOME Infrastructure Team 2018-09-21 16:17:04 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: