desktop-packages team mailing list archive

[kevin gunn <kevin.gunn@xxxxxxxxxxxxx>]

Public bug reported:

So, in the course of a unity8 package migration it got halted due to
qtcreator-plugin autopkg test failing

see here
http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

which lead me to look at the jenkins run, note its only failling on amd64 arch
and...you can see from here
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/
it started failing about 24 hrs ago with "can't init gxl"...almost certainly meaning it's unhappy with mesa.
low and behold the difference between the pasing jenkins and failing is

passing -> https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console
which uses
mesa 10.2.6-1ubuntu3

failing -> https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console
which uses 
mesa 10.3.0-0ubuntu1

So can we do a couple of things?
- revert mesa and see if that fixes the autopkgtest to confirm
- if so, please leave reverted until we find out why so we can actually continue landing our unity8/uitk/webbrowser stuff
- lastly, might be good to add qtcreator-plugin as an autopkgtest dependency to land a new mesa

sorry for marking critical, but we're sunk until we get this sorted

** Affects: mesa (Ubuntu)
     Importance: Critical
     Assignee: Maarten Lankhorst (mlankhorst)
         Status: New

** Changed in: mesa (Ubuntu)
   Importance: Undecided => Critical

** Changed in: mesa (Ubuntu)
     Assignee: (unassigned) => Maarten Lankhorst (mlankhorst)

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

Title:
  qtcreator-plugin autopkg test fails on AMD64 mesa mesa_10.3.0

Status in “mesa” package in Ubuntu:
  New

Bug description:
  So, in the course of a unity8 package migration it got halted due to
  qtcreator-plugin autopkg test failing

  see here
  http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

  which lead me to look at the jenkins run, note its only failling on amd64 arch
  and...you can see from here
  https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/
  it started failing about 24 hrs ago with "can't init gxl"...almost certainly meaning it's unhappy with mesa.
  low and behold the difference between the pasing jenkins and failing is

  passing -> https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console
  which uses
  mesa 10.2.6-1ubuntu3

  failing -> https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console
  which uses 
  mesa 10.3.0-0ubuntu1

  So can we do a couple of things?
  - revert mesa and see if that fixes the autopkgtest to confirm
  - if so, please leave reverted until we find out why so we can actually continue landing our unity8/uitk/webbrowser stuff
  - lastly, might be good to add qtcreator-plugin as an autopkgtest dependency to land a new mesa

  sorry for marking critical, but we're sunk until we get this sorted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1374131/+subscriptions