desktop-packages team mailing list archive

Thread
Date

[Bug 1352889] Re: Some Unity Autopilot tests are failing with "constructor returned NULL"

To: desktop-packages@xxxxxxxxxxxxxxxxxxx
From: Christopher Lee <1352889@xxxxxxxxxxxxxxxxxx>
Date: Tue, 23 Sep 2014 05:11:29 -0000
Reply-to: Bug 1352889 <1352889@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: autopilot-legacy (Ubuntu)
       Status: In Progress => Fix Released

** Changed in: autopilot
       Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1352889

Title:
  Some Unity Autopilot tests are failing with "constructor returned
  NULL"

Status in Autopilot:
  Invalid
Status in Unity:
  Invalid
Status in “autopilot-legacy” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Recently, some Unity 7 Autoppilot tests have begun failing with a
  "constructor returned NULL" error.  The log indicates that the call to
  Gio.DesktopAppInfo.new(desktop_file) is failing in /usr/lib/python2.7
  /dist-packages/autopilot/process/_bamf.py on line 334.

  This is causing close to 20 AP failures and is one issue blocking the
  release of Unity.

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