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 646609 - gtk+-2.24.4: /ui-tests/text-access test fails
gtk+-2.24.4: /ui-tests/text-access test fails
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: .General
2.24.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2011-04-03 10:19 UTC by Pacho Ramos
Modified: 2014-12-22 02:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pacho Ramos 2011-04-03 10:19:54 UTC 
It fails with the following error:

make[4]: Leaving directory `/home/pacho/gtk+-2.24.4/gtk'
make[3]: Leaving directory `/home/pacho/gtk+-2.24.4/gtk'
Making check in tests
make[3]: Entering directory `/home/pacho/gtk+-2.24.4/gtk/tests'
make  check-local
make[4]: Entering directory `/home/pacho/gtk+-2.24.4/gtk/tests'
TEST: testing... (pid=737)
Xlib:  extension "RANDR" missing on display ":101".
  /tests/statusbar-remove-all:                                         OK
  /ui-tests/text-access:                                               
Gtk-CRITICAL **: IA__gtk_test_create_widget: assertion `g_type_is_a (widget_type, GTK_TYPE_WIDGET)' failed
aborting...
FAIL
GTester: last random seed: R02S419ad1ee6892f89233aa2065c4075e47
Terminado
make[4]: *** [test-cwd] Error 143
make[4]: Leaving directory `/home/pacho/gtk+-2.24.4/gtk/tests'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/home/pacho/gtk+-2.24.4/gtk/tests'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/home/pacho/gtk+-2.24.4/gtk'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/home/pacho/gtk+-2.24.4/gtk'
make: *** [check-recursive] Error 1

This looks like a regression over 2.24.3

Thanks for your help on this
Comment 1 Pacho Ramos 2011-04-20 12:32:18 UTC 
Is there anything I can do to help with this?
Comment 2 Pacho Ramos 2011-05-04 15:49:58 UTC 
Is it safe to ignore this failure?
Comment 3 Javier Jardón (IRC: jjardon) 2011-05-04 19:05:07 UTC 
(In reply to comment #1)
> Is there anything I can do to help with this?

Yeah, sure ;)

You said that this seems a regression betwen 2.24.3 and 2.24.4, could you bisec the buggy commit?
Comment 4 Nirbheek Chauhan 2011-05-07 00:20:52 UTC 
The bug was actually introduced between 2.24.1 and 2.24.2. After bisection, I found:

559cb5d8abd55ee8be6ce0992e449a96bb7f5737 is the first bad commit
commit 559cb5d8abd55ee8be6ce0992e449a96bb7f5737
Author: Benjamin Otte <otte@redhat.com>
Date:   Mon Mar 7 17:11:26 2011 +0100

    build: Fix generation of gtktypefuncs.c with -g3 in CFLAGS
    
    With -g3, macros are included in the output, and that caused
    gdk_window_get_type() to be included when it shouldn't be.

:040000 040000 0ba56b1a6b3332c6f5a63569f9df21dc5b2dded4 c6b43d35afa5b0c68e7e31adc51241b2d23e46de M	gtk


Which seemed weird to me, so I reverted the commit on gtk-2-24, and tested again. And the test *does* pass with the commit reverted.
Comment 5 Pacho Ramos 2011-05-10 08:39:03 UTC 
Thanks Nirbheek :-)
Comment 6 Matthias Clasen 2014-12-22 02:12:27 UTC 
seems to work in the 2.24 branch