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 670254 - glib-2.30.2: Fails /GDateTime/new_from_unix test
glib-2.30.2: Fails /GDateTime/new_from_unix test
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2012-02-17 00:15 UTC by Jeremy Murphy
Modified: 2012-04-04 18:52 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
build.log: /GDateTime/new_from_unix test fails on amd64. (435.73 KB, text/x-log)
2012-02-17 00:15 UTC, Jeremy Murphy 		Details

Description Jeremy Murphy 2012-02-17 00:15:58 UTC 
Created attachment 207821 [details]
build.log: /GDateTime/new_from_unix test fails on amd64.

As the summary says, it fails the /GDateTime/new_from_unix test on, which 2.28.8 passes.  I'm running a (mostly) stable Gentoo 64-bit system.
Comment 1 Dan Winship 2012-02-23 13:29:28 UTC 
can you run tests/gdatetime by hand to see which assertion is failing?

also, what is the output of "date" on your computer?
Comment 2 Jeremy Murphy 2012-02-23 21:46:28 UTC 
I'll give it a go soon.

$ date
Fri Feb 24 08:45:19 EST 2012
Comment 3 Warren 2012-03-27 00:53:24 UTC 
I encountered this myself on glib-2.30.3, and narrowed it down to daylight saving.
Editing glib/glib/tests/gdatetime.c and adding the line 'tm.tm_dst = -1;' just before the call to mktime() solves the problem.  (Not providing a patch because I'm using a later version).
Comment 4 Dan Winship 2012-04-04 18:52:08 UTC 
Yup, that fixes it. Thanks.

(The test was unintentionally depending on January 1 being not during
DST, which of course would fail in Australia.)