← Back to team overview

desktop-packages team mailing list archive

[Bug 1478115] Re: running whoopsie during tests causes test failures


This bug was fixed in the package apport - 2.18-0ubuntu6

apport (2.18-0ubuntu6) wily; urgency=medium

  * Drop apport-noui from test dependencies, as whoopsie interferes with the
    test crashes while the test suite runs. (LP: #1478115)
  * Restore whoopsie dependency of apport-noui.
  * apport-noui.service: Add missing Type=oneshot, to fix restart limits with
    crashes happening in rapid succession.
  * Merge test fixes from trunk.
  * data/package-hooks/source_linux.py: Fix PEP-8 error.

 -- Martin Pitt <martin.pitt@xxxxxxxxxx>  Mon, 10 Aug 2015 11:25:07

** Changed in: apport (Ubuntu)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.

  running whoopsie during tests causes test failures

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  I've switched the apport-noui.path systemd file from:




  I've done this because with PathChanged it seemed to me that the
  whoopsie-upload-all, called by apport-noui.service, would be called
  when any file (e.g. .upload, .uploaded) were created in /var/crash.
  Naturally, this seemed excessive to me and PathExistsGlob seems like a
  better fit.  Additionally, it is worth noting that the following from
  the systemd.path documentation:

  "If a path already exists (in case of PathExists= and PathExistsGlob=)
  or a directory already is not empty (in case of DirectoryNotEmpty=) at
  the time the path unit is activated, then the configured unit is
  immediately activated as well. Something similar does not apply to
  PathChanged= and PathModified=."

  Given that it appears with PathChanged the apport-noui service would
  never be run during boot up, again not what we want.

  However, making these changes seems to have caused some strange test
  failures with the apport's tests.


  runs 47 through 55

To manage notifications about this bug go to: