[Bug 1259721] Re: Executing autopilot test suite fails to close when piped to tee

[Martin Pitt]

The linked MP fixes the hang, but with that we won't see the launched
program's stdout any more. It's a rather blunt fix, but otherwise we
need to make up our mind:

  - do we want to see subprocess stdout and be responsible for killing
our subprocesses on test case tearDown

or

  - do we not want to care about cleaning up spawned processes (e. g. we
don't guarantee that we kill them on teardown), but then we lose their
stdout

We can't have both. We can probably fix the root cause in autopilot (if
you take out remmina from autopilot/process/__init__.py it fixes this
problem as well, as remmina stays running after the test case ends), but
it might be desirable to impose this restriction on app tests that use
AP?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/1259721

Title:
  Executing autopilot test suite fails to close when piped to tee

Status in Autopilot:
  In Progress
Status in The "G" Library - GLib:
  Fix Released
Status in “gobject-introspection” package in Ubuntu:
  Fix Committed

Bug description:
  Executing "autopilot run autopilot | tee /tmp/autopilot.log" never
  closes on my trusty box. The autopilot process closes (according to
  "ps -ef") but the tee process stays open. It appears that tee is
  missing the EOF.

  I originally saw this on the CI autopilot runner:
  http://s-jenkins.ubuntu-ci:8080/job/autopilot-testrunner-otto-trusty/1390/console

  
  It appears I'm running an unreleased version:
  python-autopilot:
    Installed: 1.4+14.04.20131205.1-0ubuntu1

  python-autopilot-tests:
    Installed: 1.4+14.04.20131206.1-0ubuntu1

  Will try again with the archive version and update the report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1259721/+subscriptions