desktop-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

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.

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu)
     Assignee: (unassigned) => Sebastien Bacher (seb128)

-- 
You received this bug notification because you are a member of Desktop
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