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.upload ** Message: Monitoring successful.
** (./test_monitor:9220): WARNING **: Expected file /tmp/whoopsie-test-SLNTNX/fake.uploaded doesn't exist. Trace/breakpoint trap (core dumped) (utopic-i386)root@impulse:/home/bdmurray/source-trees/whoopsie/upstream/src/tests# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1381804 Title: whoopsie test failure since glib2.0 2.41.2-1 uploaded Status in “glib2.0” package in Ubuntu: New Bug description: The whoopsie test callback-triggered-once started to fail, on every architecture except amd64, after whoopsie version 0.2.37 was uploaded to utopic on 2014-08-29. That upload contains no changes to test_monitor or monitor. (https://launchpadlibrarian.net/183527163/whoopsie_0.2.36_0.2.37.diff.gz) We can see the test failure here: https://launchpadlibrarian.net/183527214/buildlog_ubuntu- utopic-i386.whoopsie_0.2.37_UPLOADING.txt.gz Previously the test passed: https://launchpadlibrarian.net/181010654 /buildlog_ubuntu-utopic-i386.whoopsie_0.2.36_UPLOADING.txt.gz Looking at the utopic-changes mailing list it looks like glib2.0 was uploaded between 2014-07-29 (0.2.36 upload) and 2014-08-29 (0.2.37 upload). Running the tests from whoopsie version 0.2.37 in a trusty chroot I've discovered that callback-triggered-once does pass. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1381804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp