Bug#711107: gtk+3.0: FTBFS on ia64 and mips
Hi Stephan, Thanks for your analysis! I indeed get a conditional jump based on an uninitialized variable on x86_64. I have forwarded your bug report upstream at https://bugzilla.gnome.org/show_bug.cgi?id=702370 As for the mips failure, I ran it on valgrind on x86_64 in case it was a similar issue and oh surprise, it fails under valgrind, even though there are no errors (well there are two but are suppressed, I haven't checked why but I'm assuming if they are suppressed then they are false positives). I have reported it with some more information at: https://bugzilla.gnome.org/show_bug.cgi?id=702371 I'm making an upload with your patch and with the failing treeview testcase disabled for now. Thanks again! Cheers, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711107: gtk+3.0: FTBFS on ia64 and mips
Nice job!
On Jun 15, 2013 9:44 AM, "Stephan Schreiber" wrote:
> tags 711107 - help
> tags 711107 + patch
> thanks
>
>
> Emilio Pozuelo Monfort wrote:
>
> What happens if you do `make check' or `fakeroot make check' again? make
>> check
>> will set Xvfb differently than xvfb-run.
>>
>
> I didn't check that out. I assume the test will always fail with 'make
> check'.
> It doesn't matter what X server you are using, or how xvfb is set.
>
> The test fails when gtester is invoked:
> xvfb-run gtester -k --verbose children
> fails, but
> xvfb-run ./children
> passes the test.
>
> This is very interesting, but a misleading and useless information ;-).
> The real problem is in the tests/a11y/children.c source code file within
> the test_add_remove() function; it reads local variables without
> initialization:
>
> static void
> test_add_remove (GtkWidget *widget)
> {
> AtkObject *accessible;
> AtkObject *child_accessible;
> SignalData add_data;
> SignalData remove_data;
> SignalData parent_data[3];
> STATE state;
> gint i, j;
> gint step_children;
>
> state.widget = widget;
> accessible = gtk_widget_get_accessible (widget);
>
> add_data.count = 0;
> remove_data.count = 0;
> g_signal_connect (accessible, "children_changed::add",
> G_CALLBACK (children_changed), &add_data);
> g_signal_connect (accessible, "children_changed::remove",
> G_CALLBACK (children_changed), &remove_data);
>
> step_children = atk_object_get_n_accessible_**children (accessible);
>
> for (i = 0; i < 3; i++)
> {
> if (!do_create_child (&state, i))
> break;
> if (!GTK_IS_ENTRY (widget))
> {
> parent_data[i].count = 0;
> child_accessible = gtk_widget_get_accessible (state.child[i]);
> g_signal_connect (child_accessible, "notify::accessible-parent",
> G_CALLBACK (parent_notify), &(parent_data[i]));
> gtk_container_add (GTK_CONTAINER (widget), state.child[i]);
> }
> else
> child_accessible = atk_object_ref_accessible_**child (accessible,
> i);
>
> g_assert_cmpint (add_data.count, ==, i + 1);
> g_assert_cmpint (add_data.n_children, ==, step_children + i + 1);
> g_assert_cmpint (remove_data.count, ==, 0);
> if (!GTK_IS_ENTRY (widget))
> g_assert_cmpint (parent_data[i].count, ==, 1);
> if (GTK_IS_SCROLLED_WINDOW (widget) ||
> GTK_IS_NOTEBOOK (widget))
> g_assert (atk_object_get_parent (ATK_OBJECT
> (parent_data[i].parent)) == accessible);
> else if (GTK_IS_ENTRY (widget))
> g_assert (atk_object_get_parent (child_accessible) == accessible);
> else
> g_assert (parent_data[i].parent == accessible);
>
> if (GTK_IS_ENTRY (widget))
> g_object_unref (child_accessible);
> }
> for (j = 0 ; j < i; j++)
> {
> remove_child (&state, j);
> g_assert_cmpint (add_data.count, ==, i);
> g_assert_cmpint (remove_data.count, ==, j + 1);
> g_assert_cmpint (remove_data.n_children, ==, step_children + i - j -
> 1);
> if (parent_data[j].count == 2)
> g_assert (parent_data[j].parent == NULL);
> else if (!GTK_IS_ENTRY (widget))
> {
> AtkStateSet *set;
> set = atk_object_ref_state_set (ATK_OBJECT
> (parent_data[j].parent));
> g_assert (atk_state_set_contains_state (set, ATK_STATE_DEFUNCT));
> g_object_unref (set);
> }
> }
>
> g_signal_handlers_disconnect_**by_func (accessible, G_CALLBACK
> (children_changed), &add_data);
> g_signal_handlers_disconnect_**by_func (accessible, G_CALLBACK
> (children_changed), &remove_data);
> }
>
>
> When you take a look at the main() function in children.c, you realize
> that test_add_remove() is called multiple times; it gets via its widget
> paramter object instances of different types.
> Almost all object types are derived from GtkWidget or GtkContainer;
> GTK_IS_ENTRY() evaluates to false for them.
> The last type is GtkEntry (created by gtk_entry_new()); GTK_IS_ENTRY()
> evaluates to true for it. This is the test we have the trouble with.
>
>
> Please take a look at the fifth line within the function:
> SignalData parent_data[3];
>
> Let's assume that we are running the buggy test; widget is a GtkEntry
> instance; GTK_IS_ENTRY (widget) is true.
> The first time you see some code for parent_data[].count is in the first
> for loop. But if GTK_IS_ENTRY (widget) is true, parent_data isnt'touched at
> all. No pointer to parent_data is provided to somewhere else:
>
> if (!GTK_IS_ENTRY (widget))
> {
> parent_data[i].count = 0;
> child_accessible = gtk_widget_get_accessible (state.child[i]);
> g_signal_connect (child_accessible, "notify::accessible-parent",
> G_CALLBACK (parent_notify), &(parent_data[i]));
> ...
> }
> else
> child_accessible =
Processed: Re: Bug#711107: gtk+3.0: FTBFS on ia64 and mips
Processing commands for cont...@bugs.debian.org: > tags 711107 - help Bug #711107 [src:gtk+3.0] gtk+3.0: FTBFS on ia64 and mips Removed tag(s) help. > tags 711107 + patch Bug #711107 [src:gtk+3.0] gtk+3.0: FTBFS on ia64 and mips Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 711107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711107: gtk+3.0: FTBFS on ia64 and mips
tags 711107 - help
tags 711107 + patch
thanks
Emilio Pozuelo Monfort wrote:
What happens if you do `make check' or `fakeroot make check' again?
make check
will set Xvfb differently than xvfb-run.
I didn't check that out. I assume the test will always fail with 'make check'.
It doesn't matter what X server you are using, or how xvfb is set.
The test fails when gtester is invoked:
xvfb-run gtester -k --verbose children
fails, but
xvfb-run ./children
passes the test.
This is very interesting, but a misleading and useless information ;-).
The real problem is in the tests/a11y/children.c source code file
within the test_add_remove() function; it reads local variables
without initialization:
static void
test_add_remove (GtkWidget *widget)
{
AtkObject *accessible;
AtkObject *child_accessible;
SignalData add_data;
SignalData remove_data;
SignalData parent_data[3];
STATE state;
gint i, j;
gint step_children;
state.widget = widget;
accessible = gtk_widget_get_accessible (widget);
add_data.count = 0;
remove_data.count = 0;
g_signal_connect (accessible, "children_changed::add",
G_CALLBACK (children_changed), &add_data);
g_signal_connect (accessible, "children_changed::remove",
G_CALLBACK (children_changed), &remove_data);
step_children = atk_object_get_n_accessible_children (accessible);
for (i = 0; i < 3; i++)
{
if (!do_create_child (&state, i))
break;
if (!GTK_IS_ENTRY (widget))
{
parent_data[i].count = 0;
child_accessible = gtk_widget_get_accessible (state.child[i]);
g_signal_connect (child_accessible, "notify::accessible-parent",
G_CALLBACK (parent_notify), &(parent_data[i]));
gtk_container_add (GTK_CONTAINER (widget), state.child[i]);
}
else
child_accessible = atk_object_ref_accessible_child (accessible, i);
g_assert_cmpint (add_data.count, ==, i + 1);
g_assert_cmpint (add_data.n_children, ==, step_children + i + 1);
g_assert_cmpint (remove_data.count, ==, 0);
if (!GTK_IS_ENTRY (widget))
g_assert_cmpint (parent_data[i].count, ==, 1);
if (GTK_IS_SCROLLED_WINDOW (widget) ||
GTK_IS_NOTEBOOK (widget))
g_assert (atk_object_get_parent (ATK_OBJECT
(parent_data[i].parent)) == accessible);
else if (GTK_IS_ENTRY (widget))
g_assert (atk_object_get_parent (child_accessible) == accessible);
else
g_assert (parent_data[i].parent == accessible);
if (GTK_IS_ENTRY (widget))
g_object_unref (child_accessible);
}
for (j = 0 ; j < i; j++)
{
remove_child (&state, j);
g_assert_cmpint (add_data.count, ==, i);
g_assert_cmpint (remove_data.count, ==, j + 1);
g_assert_cmpint (remove_data.n_children, ==, step_children + i - j - 1);
if (parent_data[j].count == 2)
g_assert (parent_data[j].parent == NULL);
else if (!GTK_IS_ENTRY (widget))
{
AtkStateSet *set;
set = atk_object_ref_state_set (ATK_OBJECT (parent_data[j].parent));
g_assert (atk_state_set_contains_state (set, ATK_STATE_DEFUNCT));
g_object_unref (set);
}
}
g_signal_handlers_disconnect_by_func (accessible, G_CALLBACK
(children_changed), &add_data);
g_signal_handlers_disconnect_by_func (accessible, G_CALLBACK
(children_changed), &remove_data);
}
When you take a look at the main() function in children.c, you realize
that test_add_remove() is called multiple times; it gets via its
widget paramter object instances of different types.
Almost all object types are derived from GtkWidget or GtkContainer;
GTK_IS_ENTRY() evaluates to false for them.
The last type is GtkEntry (created by gtk_entry_new()); GTK_IS_ENTRY()
evaluates to true for it. This is the test we have the trouble with.
Please take a look at the fifth line within the function:
SignalData parent_data[3];
Let's assume that we are running the buggy test; widget is a GtkEntry
instance; GTK_IS_ENTRY (widget) is true.
The first time you see some code for parent_data[].count is in the
first for loop. But if GTK_IS_ENTRY (widget) is true, parent_data
isnt'touched at all. No pointer to parent_data is provided to
somewhere else:
if (!GTK_IS_ENTRY (widget))
{
parent_data[i].count = 0;
child_accessible = gtk_widget_get_accessible (state.child[i]);
g_signal_connect (child_accessible, "notify::accessible-parent",
G_CALLBACK (parent_notify), &(parent_data[i]));
...
}
else
child_accessible = atk_object_ref_accessible_child (accessible, i);
In the second for loop:
if (parent_data[j].count == 2)
g_assert (parent_data[j].parent == NULL);
else if (!GTK_IS_ENTRY (widget))
parent_data is read here without any preceding initialization. Thus,
we are running into tro
Bug#711107: gtk+3.0: FTBFS on ia64 and mips
Hi, On 15/06/13 04:01, Stephan Schreiber wrote: > I'm using Debian unstable on ia64. > > I built the gtk+3.0 package twice; the test always fails as on the ia64 > buildd: > > /usr/bin/make check-local > make[4]: Entering directory > `/home/stephan/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y' > TEST: accessibility-dump... (pid=3867) > PASS: accessibility-dump > TEST: tree-performance... (pid=3889) > PASS: tree-performance > TEST: text... (pid=3908) > /text/bold/GtkLabel: OK > /text/basic/GtkLabel:OK > /text/basic/GtkEntry:OK > /text/basic/GtkTextView: OK > /text/words/GtkLabel:OK > /text/words/GtkEntry:OK > /text/words/GtkTextView: OK > /text/changed/GtkLabel: OK > /text/changed/GtkEntry: OK > /text/changed/GtkTextView: OK > /text/selection/GtkLabel:OK > /text/selection/GtkEntry:OK > /text/selection/GtkTextView: OK > PASS: text > TEST: children... (pid=3927) > /scrolledwindow/child-count: OK > /child/add-remove/GtkScrolledWindow: OK > /child/add-remove/GtkBox:OK > /child/add-remove/GtkPaned: OK > /child/add-remove/GtkGrid: OK > /child/add-remove/GtkEventBox: OK > /child/add-remove/GtkWindow: OK > /child/add-remove/GtkAssistant: OK > /child/add-remove/GtkFrame: OK > /child/add-remove/GtkExpander: OK > /child/add-remove/GtkTable: OK > /child/add-remove/GtkTextView: OK > /child/add-remove/GtkTreeView: OK > /child/add-remove/GtkNotebook: OK > /child/add-remove/GtkEntry: ** > ERROR:/home/stephan/gtkplus2/gtk+3.0-3.8.2/./tests/a11y/children.c:201:test_add_remove: > assertion failed: (parent_data[j].parent == NULL) > FAIL > GTester: last random seed: R02S2c373dee33e29d116c561db135f16945 > (pid=3946) > FAIL: children > TEST: derive... (pid=3960) > PASS: derive > TEST: value... (pid=3979) > /value/basic/GtkSpinButton: OK > /value/basic/GtkLevelBar:OK > PASS: value > TEST: tree-relationships... (pid=3998) > /a11y/tree/focus:OK > /a11y/tree/relations:OK > PASS: tree-relationships > TEST: util... (pid=4018) > /util/toolkit-name: OK > /util/toolkit-version: OK > /util/root: OK > PASS: util > make[4]: *** [test-cwd] Error 1 > make[4]: Target `check-local' not remade because of errors. > make[4]: Leaving directory > `/home/stephan/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y' > make[3]: *** [check-am] Error 2 > make[3]: Target `check' not remade because of errors. > make[3]: Leaving directory > `/home/stephan/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y' > > > > The test passes when I run it subsequently: > > stephan@itanic:~/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y$ > xvfb-run > ./children > /scrolledwindow/child-count: OK > /child/add-remove/GtkScrolledWindow: OK > /child/add-remove/GtkBox: OK > /child/add-remove/GtkPaned: OK > /child/add-remove/GtkGrid: OK > /child/add-remove/GtkEventBox: OK > /child/add-remove/GtkWindow: OK > /child/add-remove/GtkAssistant: OK > /child/add-remove/GtkFrame: OK > /child/add-remove/GtkExpander: OK > /child/add-remove/GtkTable: OK > /child/add-remove/GtkTextView: OK > /child/add-remove/GtkTreeView: OK > /child/add-remove/GtkNotebook: OK > /child/add-remove/GtkEntry: OK > > > > It works with fakeroot as well: > > stephan@itanic:~/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y$ > fakeroot > xvfb-run ./children > /scrolledwindow/child-count: OK > /child/add-remove/GtkScrolledWindow: OK > /child/add-remove/GtkBox: OK > /child/add-remove/GtkPaned: OK > /child/add-remove/GtkGrid:
Bug#711107: gtk+3.0: FTBFS on ia64 and mips
I'm using Debian unstable on ia64. I built the gtk+3.0 package twice; the test always fails as on the ia64 buildd: /usr/bin/make check-local make[4]: Entering directory `/home/stephan/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y' TEST: accessibility-dump... (pid=3867) PASS: accessibility-dump TEST: tree-performance... (pid=3889) PASS: tree-performance TEST: text... (pid=3908) /text/bold/GtkLabel: OK /text/basic/GtkLabel:OK /text/basic/GtkEntry:OK /text/basic/GtkTextView: OK /text/words/GtkLabel:OK /text/words/GtkEntry:OK /text/words/GtkTextView: OK /text/changed/GtkLabel: OK /text/changed/GtkEntry: OK /text/changed/GtkTextView: OK /text/selection/GtkLabel:OK /text/selection/GtkEntry:OK /text/selection/GtkTextView: OK PASS: text TEST: children... (pid=3927) /scrolledwindow/child-count: OK /child/add-remove/GtkScrolledWindow: OK /child/add-remove/GtkBox:OK /child/add-remove/GtkPaned: OK /child/add-remove/GtkGrid: OK /child/add-remove/GtkEventBox: OK /child/add-remove/GtkWindow: OK /child/add-remove/GtkAssistant: OK /child/add-remove/GtkFrame: OK /child/add-remove/GtkExpander: OK /child/add-remove/GtkTable: OK /child/add-remove/GtkTextView: OK /child/add-remove/GtkTreeView: OK /child/add-remove/GtkNotebook: OK /child/add-remove/GtkEntry: ** ERROR:/home/stephan/gtkplus2/gtk+3.0-3.8.2/./tests/a11y/children.c:201:test_add_remove: assertion failed: (parent_data[j].parent == NULL) FAIL GTester: last random seed: R02S2c373dee33e29d116c561db135f16945 (pid=3946) FAIL: children TEST: derive... (pid=3960) PASS: derive TEST: value... (pid=3979) /value/basic/GtkSpinButton: OK /value/basic/GtkLevelBar:OK PASS: value TEST: tree-relationships... (pid=3998) /a11y/tree/focus:OK /a11y/tree/relations:OK PASS: tree-relationships TEST: util... (pid=4018) /util/toolkit-name: OK /util/toolkit-version: OK /util/root: OK PASS: util make[4]: *** [test-cwd] Error 1 make[4]: Target `check-local' not remade because of errors. make[4]: Leaving directory `/home/stephan/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y' make[3]: *** [check-am] Error 2 make[3]: Target `check' not remade because of errors. make[3]: Leaving directory `/home/stephan/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y' The test passes when I run it subsequently: stephan@itanic:~/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y$ xvfb-run ./children /scrolledwindow/child-count: OK /child/add-remove/GtkScrolledWindow: OK /child/add-remove/GtkBox: OK /child/add-remove/GtkPaned: OK /child/add-remove/GtkGrid: OK /child/add-remove/GtkEventBox: OK /child/add-remove/GtkWindow: OK /child/add-remove/GtkAssistant: OK /child/add-remove/GtkFrame: OK /child/add-remove/GtkExpander: OK /child/add-remove/GtkTable: OK /child/add-remove/GtkTextView: OK /child/add-remove/GtkTreeView: OK /child/add-remove/GtkNotebook: OK /child/add-remove/GtkEntry: OK It works with fakeroot as well: stephan@itanic:~/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y$ fakeroot xvfb-run ./children /scrolledwindow/child-count: OK /child/add-remove/GtkScrolledWindow: OK /child/add-remove/GtkBox: OK /child/add-remove/GtkPaned: OK /child/add-remove/GtkGrid: OK /child/add-remove/GtkEventBox: OK /child/add-remove/GtkWindow: OK /child/add-remove/GtkAssistant: OK /child/add-remove/GtkFrame: OK /child/add-remove/GtkExpander: OK /child/add-remove/GtkTable: OK /child/add-remove/GtkTextView: OK /child/add-
Bug#711107: gtk+3.0: FTBFS on ia64 and mips
OK, I turned on my machine and re-ran the 'a11y/children' test. It worked just fine under X and Xvfb when I ran it as just "./children" and "xvfb-run ./children" respectively -- I get OK messages like you wrote initially and no assertion failures. Next I deleted the whole gtk+3.0 directory, redownloaded the source, and rebuilt it. I hit the same error: WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files --- If anyone has an idea why running this before building gtk+3.0 is ok, but running it afterwards fails, I'd love to know. I can say that whatever the original problem (assertion failure in children.c) was, I didn't seem to run into it. Patrick On Wed, Jun 12, 2013 at 10:17 AM, Emilio Pozuelo Monfort wrote: > On 12/06/13 16:48, Patrick Baggett wrote: > > Hi Emilio, > > > > I have an ia64 box with local graphics adapter and working X server. > Pardon > > the newbie question -- do I use apt-get to pull the source and then build > > it using "make test" or some other procedure? > > That's great! Something like this should work: > > apt-get update > apt-get source gtk+3.0 > apt-get build-dep gtk+3.0 > cd gtk+3.0-3.8.2 > dpkg-buildpackage -us -uc > > At some point the build will fail (when running the tests). Then do: > > cd debian/build/shared/tests/a11y > > ./children > > And see if the test passes. And > > xvfb-run ./children > > And see if it fails. > > Thanks! > Emilio >
Bug#711107: gtk+3.0: FTBFS on ia64 and mips
On 12/06/13 16:48, Patrick Baggett wrote: > Hi Emilio, > > I have an ia64 box with local graphics adapter and working X server. Pardon > the newbie question -- do I use apt-get to pull the source and then build > it using "make test" or some other procedure? That's great! Something like this should work: apt-get update apt-get source gtk+3.0 apt-get build-dep gtk+3.0 cd gtk+3.0-3.8.2 dpkg-buildpackage -us -uc At some point the build will fail (when running the tests). Then do: cd debian/build/shared/tests/a11y ./children And see if the test passes. And xvfb-run ./children And see if it fails. Thanks! Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711107: gtk+3.0: FTBFS on ia64 and mips
Hi Emilio, I have an ia64 box with local graphics adapter and working X server. Pardon the newbie question -- do I use apt-get to pull the source and then build it using "make test" or some other procedure? Patrick On Wed, Jun 12, 2013 at 6:45 AM, Emilio Pozuelo Monfort wrote: > tags 711107 + help > thanks > > Hi, > > On 04/06/13 20:45, Adam D. Barratt wrote: > > Source: gtk+3.0 > > Version: 3.8.2-1 > > Severity: serious > > Tags: jessie sid > > > > Hi, > > > > gtk+3.0 FTBFS on ia64 and mips with test errors. From the ia64 build > > log: > > > > TEST: children... (pid=30825) > > process 30825: D-Bus library appears to be incorrectly set up; failed to > read machine uuid: Failed to open "/etc/machine-id": No such file or > directory > > See the manual page for dbus-uuidgen to correct this issue. > > /scrolledwindow/child-count: OK > > /child/add-remove/GtkScrolledWindow: OK > > /child/add-remove/GtkBox:OK > > /child/add-remove/GtkPaned: OK > > /child/add-remove/GtkGrid: OK > > /child/add-remove/GtkEventBox: OK > > /child/add-remove/GtkWindow: OK > > /child/add-remove/GtkAssistant: OK > > /child/add-remove/GtkFrame: OK > > /child/add-remove/GtkExpander: OK > > /child/add-remove/GtkTable: OK > > /child/add-remove/GtkTextView: OK > > /child/add-remove/GtkTreeView: OK > > /child/add-remove/GtkNotebook: OK > > ** > > > ERROR:/build/buildd-gtk+3.0_3.8.2-1-ia64-B1rOQa/gtk+3.0-3.8.2/./tests/a11y/children.c:201:test_add_remove: > assertion failed: (parent_data[j].parent == NULL) > > /child/add-remove/GtkEntry: > FAIL > > GTester: last random seed: R02Sae645f89bea2b5a42d0ff294fe8decbd > > (pid=30845) > > process 30845: D-Bus library appears to be incorrectly set up; failed to > read machine uuid: Failed to open "/etc/machine-id": No such file or > directory > > See the manual page for dbus-uuidgen to correct this issue. > > FAIL: children > > I built gtk+3.0 in a mips and an ia64 porterboxes and reproduced the > failures > (note they are different failures, the one above is for ia64). I had a > look at > the source and couldn't find anything obviously wrong. Those tests pass on > every > other architecture. Note that the tests run under Xvfb (see the Makefile). > I > could reproduce the tests by running make check or by running xvfb-run > ./children (or the mips failing test). I wanted to make sure this wasn't a > problem with xvfb by running this with a real display, but apparently X > forwarding is disabled on the buildds. > > Help here is appreciated. I would suggest to first try these tests in a > real > display to rule out Xvfb issues. > > Thanks, > Emilio > > > -- > To UNSUBSCRIBE, email to debian-ia64-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/51b85f4b.90...@debian.org > >
Processed: Re: Bug#711107: gtk+3.0: FTBFS on ia64 and mips
Processing commands for cont...@bugs.debian.org: > tags 711107 + help Bug #711107 [src:gtk+3.0] gtk+3.0: FTBFS on ia64 and mips Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 711107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711107: gtk+3.0: FTBFS on ia64 and mips
tags 711107 + help thanks Hi, On 04/06/13 20:45, Adam D. Barratt wrote: > Source: gtk+3.0 > Version: 3.8.2-1 > Severity: serious > Tags: jessie sid > > Hi, > > gtk+3.0 FTBFS on ia64 and mips with test errors. From the ia64 build > log: > > TEST: children... (pid=30825) > process 30825: D-Bus library appears to be incorrectly set up; failed to read > machine uuid: Failed to open "/etc/machine-id": No such file or directory > See the manual page for dbus-uuidgen to correct this issue. > /scrolledwindow/child-count: OK > /child/add-remove/GtkScrolledWindow: OK > /child/add-remove/GtkBox:OK > /child/add-remove/GtkPaned: OK > /child/add-remove/GtkGrid: OK > /child/add-remove/GtkEventBox: OK > /child/add-remove/GtkWindow: OK > /child/add-remove/GtkAssistant: OK > /child/add-remove/GtkFrame: OK > /child/add-remove/GtkExpander: OK > /child/add-remove/GtkTable: OK > /child/add-remove/GtkTextView: OK > /child/add-remove/GtkTreeView: OK > /child/add-remove/GtkNotebook: OK > ** > ERROR:/build/buildd-gtk+3.0_3.8.2-1-ia64-B1rOQa/gtk+3.0-3.8.2/./tests/a11y/children.c:201:test_add_remove: > assertion failed: (parent_data[j].parent == NULL) > /child/add-remove/GtkEntry: FAIL > GTester: last random seed: R02Sae645f89bea2b5a42d0ff294fe8decbd > (pid=30845) > process 30845: D-Bus library appears to be incorrectly set up; failed to read > machine uuid: Failed to open "/etc/machine-id": No such file or directory > See the manual page for dbus-uuidgen to correct this issue. > FAIL: children I built gtk+3.0 in a mips and an ia64 porterboxes and reproduced the failures (note they are different failures, the one above is for ia64). I had a look at the source and couldn't find anything obviously wrong. Those tests pass on every other architecture. Note that the tests run under Xvfb (see the Makefile). I could reproduce the tests by running make check or by running xvfb-run ./children (or the mips failing test). I wanted to make sure this wasn't a problem with xvfb by running this with a real display, but apparently X forwarding is disabled on the buildds. Help here is appreciated. I would suggest to first try these tests in a real display to rule out Xvfb issues. Thanks, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711107: gtk+3.0: FTBFS on ia64 and mips
Source: gtk+3.0 Version: 3.8.2-1 Severity: serious Tags: jessie sid Hi, gtk+3.0 FTBFS on ia64 and mips with test errors. From the ia64 build log: TEST: children... (pid=30825) process 30825: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory See the manual page for dbus-uuidgen to correct this issue. /scrolledwindow/child-count: OK /child/add-remove/GtkScrolledWindow: OK /child/add-remove/GtkBox:OK /child/add-remove/GtkPaned: OK /child/add-remove/GtkGrid: OK /child/add-remove/GtkEventBox: OK /child/add-remove/GtkWindow: OK /child/add-remove/GtkAssistant: OK /child/add-remove/GtkFrame: OK /child/add-remove/GtkExpander: OK /child/add-remove/GtkTable: OK /child/add-remove/GtkTextView: OK /child/add-remove/GtkTreeView: OK /child/add-remove/GtkNotebook: OK ** ERROR:/build/buildd-gtk+3.0_3.8.2-1-ia64-B1rOQa/gtk+3.0-3.8.2/./tests/a11y/children.c:201:test_add_remove: assertion failed: (parent_data[j].parent == NULL) /child/add-remove/GtkEntry: FAIL GTester: last random seed: R02Sae645f89bea2b5a42d0ff294fe8decbd (pid=30845) process 30845: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory See the manual page for dbus-uuidgen to correct this issue. FAIL: children [...] make[1]: *** [check-recursive] Error 1 make[1]: Target `check' not remade because of errors. make[1]: Leaving directory `/build/buildd-gtk+3.0_3.8.2-1-ia64-B1rOQa/gtk+3.0-3.8.2/debian/build/shared' make: *** [debian/stamp-makefile-check/shared] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Full logs available via https://buildd.debian.org/status/package.php?p=gtk%2b3.0 Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
