/GDateTime/new_full: OK /GDateTime/now: OK /GDateTime/printf: ** ERROR:gdatetime.c:846:test_GDateTime_printf: assertion failed (__p == (dst)): ("Local time zone must be set--see zic manual page" == " \222\337") FAIL GTester: last random seed: R02S5ff54ce6dd464757145766ddd67a05cd /bin/sh: line 1: 18525 Terminated MALLOC_CHECK_=2 MALLOC_PERTURB_=$((${RANDOM:-256} % 256)) ../../glib/gtester --verbose testing option-context option-argv0 keyfile fileutils test-printf protocol rand strfuncs string markup-parse markup-collect markup-escape markup-subparser array-test hostutils gvariant mem-overflow utf8-performance utils regex base64 sequence scannerapi shell collate utf8-pointer utf8-validate utf8-misc unicode checksum hmac hash cache date node convert list slist queue tree uri dir pattern logging error bookmarkfile gdatetime timeout environment mappedfile dataset sort unix unix-nothreads bitlock make[4]: *** [test-nonrecursive] Error 143 make[4]: Leaving directory `/var/tmp/portage/dev-libs/glib-2.30.3/work/glib-2.30.3/glib/tests' make[3]: *** [check-am] Error 2 make[3]: Leaving directory `/var/tmp/portage/dev-libs/glib-2.30.3/work/glib-2.30.3/glib/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/dev-libs/glib-2.30.3/work/glib-2.30.3/glib' make[1]: *** [check] Error 2 make[1]: Leaving directory `/var/tmp/portage/dev-libs/glib-2.30.3/work/glib-2.30.3/glib' make: *** [check-recursive] Error 1 * ERROR: dev-libs/glib-2.30.3 failed (test phase): * emake failed
Should we consider having not timezone set like a "valid" setup? Per error message looks like gdatetime dies intentionally :-/
The test is failing correctly. If the system timezone is not set, then GDateTime's g_date_time_get_timezone_abbreviation() can be expected fail. Users who do not follow the handbook, and do not create /etc/localtime when setting up their system, should expect some software to fail.
