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 700244 - gtk/tests/.libs/filechooser:6056): Gtk-CRITICAL **: IA__gtk_widget_get_accessible: assertion `GTK_IS_WIDGET (widget)' failed
gtk/tests/.libs/filechooser:6056): Gtk-CRITICAL **: IA__gtk_widget_get_access...
Status: RESOLVED INCOMPLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.24.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2013-05-13 19:01 UTC by Pacho Ramos
Modified: 2017-08-19 15:09 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
build.log (1.50 MB, text/x-log)
2013-05-13 19:02 UTC, Pacho Ramos 		Details

Description Pacho Ramos 2013-05-13 19:01:29 UTC 
We get this test failure:
(/var/tmp/portage/x11-libs/gtk+-2.24.18/work/gtk+-2.24.18/gtk/tests/.libs/filechooser:6056): Gtk-CRITICAL **: IA__gtk_widget_get_accessible: assertion `GTK_IS_WIDGET (widget)' failed
FAIL
GTester: last random seed: R02Sa70a606327f26dae92e871fd244a3f9f
Terminado
make[4]: *** [test-cwd] Error 143
make[4]: Leaving directory `/var/tmp/portage/x11-libs/gtk+-2.24.18/work/gtk+-2.24.18/gtk/tests'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/var/tmp/portage/x11-libs/gtk+-2.24.18/work/gtk+-2.24.18/gtk/tests'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/x11-libs/gtk+-2.24.18/work/gtk+-2.24.18/gtk'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/var/tmp/portage/x11-libs/gtk+-2.24.18/work/gtk+-2.24.18/gtk'
make: *** [check-recursive] Error 1

Full build.log attached
Comment 1 Pacho Ramos 2013-05-13 19:02:06 UTC 
Created attachment 244083 [details]
build.log
Comment 2 Matthias Clasen 2013-05-20 01:24:48 UTC 
Filing all these build failures without further analysis is not very useful - we see the tests failing ourselves...
Comment 3 Pacho Ramos 2013-05-20 06:43:36 UTC 
If you were seeing it yourselves, I guess it's not major enough and we can safely use this version of gtk+? (also, why isn't the test skipped if it's known to fail?)
Comment 4 Daniel Boles 2017-08-19 15:09:21 UTC 
Either not major enough, or no one has yet looked into it, for example by analysing a stack trace from the failed assertion, which is the key thing missing here.

If this is still an issue, please do reopen if you can post info that could help resolve it.

But I doubt it is, since I can't find an equivalent test in either tests/ or testsuite/gtk, and the one I did find - testfilechooser - does not immediately seem to have any problems.