Posting on behalf of Ryan, who cannot log in right now.
He found out that the problem is in the test case itself. It uses
g_main_loop_quit() as a source callback from
test_callback_never_triggered. Source callbacks are supposed to return
bool for if they get issued again or not. Apparently on amd6
Ryan said he's going to have a look, thanks!
** Changed in: glib2.0 (Ubuntu)
Assignee: Sebastien Bacher (seb128) => Ryan Lortie (desrt)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net
Seb, can I ask that you (or someone on desktop) look at this, please?
The whoopsie tests clearly need to be made autopkgtests, so that they're
run at the right moment for catching glib2.0 regressions, but as that
didn't happen, it's rather urgent now to figure out the cause of this
problem.
** Cha
And here we can see the test failing in a utopic-i386 chroot.
/whoopsie/callback-triggered-once: ** Message: g_signal_connecting.
** Message: Callback registered.
** Message: crash file created: /tmp/whoopsie-test-SLNTNX/fake.crash
** Message: upload file work done: /tmp/whoopsie-test-SLNTNX/fake.
Here we can see the test passing in a trusty-i386 chroot. (I've added
some g_message calls to the test_monitor.c and monitor.c.)
/whoopsie/callback-triggered-once: ** Message: g_signal_connecting.
** Message: Callback registered.
** Message: crash file created: /tmp/whoopsie-test-7SOTNX/fake.crash
