Autopilot cannot attach process stdout or stderr that contain non-ascii characters

Bug #1278272 reported by Thomi Richards on 2014-02-10
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Autopilot
Critical
Unassigned
autopilot (Ubuntu)
Undecided
Unassigned

Bug Description

Autopilot fails to attach the process stdout or stderr of any launched test app when that app contains non-ascii characters.

Related branches

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package autopilot - 1.4+14.04.20140212-0ubuntu1

---------------
autopilot (1.4+14.04.20140212-0ubuntu1) trusty; urgency=low

  [ CI bot ]
  * Resync trunk

  [ Christopher Lee ]
  * Deprecating the use of AutopilotTestCase.pick_app_launcher
  * Fix a regression in the "autopilot launch" command which meant that
    application arguments were taken as the application to launch. (LP:
    #1275913)

  [ Thomi Richards ]
  * Remove ibus.py from autopilot, as it should live in lp:unity. (LP:
    #1210661)
  * Add unit tests to the autopilot.run module.
  * Refactor parts of the 'autopilot.run' module, adding unit tests and
    simplifying the code along the way.
  * Fix docs WRT Eventually matcher's interaction with Raises() matcher.
    (LP: #1244490)
  * Get display resolution using fbset, falling back to hard coded
    values based on image codename on phablet devices.
  * Fix functional tests that started failing when window-mocker
    changed. (LP: #1278187)
  * Add unit tests for missing coverage on code that picks device
    backends at runtime.
  * Fix a bug where autopilot didn't do the right thing with non-unicode
    valid bytestrings. (LP: #1278272)
 -- Ubuntu daily release <email address hidden> Wed, 12 Feb 2014 01:14:02 +0000

Changed in autopilot (Ubuntu):
status: New → Fix Released
Changed in autopilot:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers