touch-packages team mailing list archive

[Launchpad Bug Tracker <1381804@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package whoopsie - 0.2.39

---------------
whoopsie (0.2.39) utopic; urgency=medium

  * Use G_SOURCE_CONTINUE and G_SOURCE_REMOVE for GSourceFunc return values,
    for clarity
  * tests/monitor: Call g_main_loop_quit from a callback function which
    removes the source instead of directly. GSourceFuncs need to return a
    boolean to say if they should be executed again or not. (LP: #1381804)
 -- Iain Lane <iain.lane@xxxxxxxxxxxxx>   Thu, 16 Oct 2014 10:32:22 +0100

** Branch linked: lp:ubuntu/utopic-proposed/whoopsie

** Changed in: whoopsie (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1381804

Title:
  whoopsie test failure since glib2.0 2.41.2-1 uploaded

Status in “whoopsie” package in Ubuntu:
  Fix Released

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/whoopsie/+bug/1381804/+subscriptions