qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0

Bug #1374131 reported by kevin gunn
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Fix Released
Critical
Maarten Lankhorst

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

kevin gunn (kgunn72)
Changed in mesa (Ubuntu):
importance: Undecided → Critical
assignee: nobody → Maarten Lankhorst (mlankhorst)
Andy Whitcroft (apw)
tags: added: block-proposed blocks-proposed
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mesa (Ubuntu):
status: New → Confirmed
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Also blocks qtbase from landing / running its unit tests successfully bug #1374355

Colin Watson (cjwatson)
summary: - qtcreator-plugin autopkg test fails on AMD64 mesa mesa_10.3.0
+ qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0
tags: removed: blocks-proposed
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

I've removed mesa from utopic-proposed for the time being, pending investigation.

Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

I've managed to reproduce this. This seems to be caused because swrast is now linked into the gallium megablob as well.
Before llvmpipe was statically linked into libGL.so

Adding a depends on libgl1-mesa-dri to libegl1-mesa and libgl1-mesa-glx should fix things. I'm verifying this in a ppa.

Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

Ok, it also seems that libgbm1 was pulling in libgl1-mesa-dri directly in 10.2.6, this is why libgl1-mesa-dri was installed in the first place.

/usr/lib/$ARCH/gbm/gbm_gallium_drm.so was linking to the shared libgallium.so . This no longer happens with 10.3.0 because we drop the patches that build gallium shared, because upstream handles it better.

I would say this proves that the tests are all broken and need to add an explicit depend on libgl1-mesa-dri somewhere.

But since this has been going on for so long I think the easiest thing to do is fixing up the mesa packaging for backwards compatability.

tags: removed: block-proposed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mesa - 10.3.0-0ubuntu2

---------------
mesa (10.3.0-0ubuntu2) utopic; urgency=medium

  * Add depends on libgl1-mesa-dri to some packages.
    - libgl1-mesa-glx, libegl1-mesa and libgbm1 depend on the dri
      files to be installed, even for swrast support. (LP: #1374131)

mesa (10.3.0-0ubuntu1) utopic; urgency=medium

  * New upstream release. (LP: #1364003)
  * Merge from released debian-experimental.

mesa (10.3.0-1) UNRELEASED; urgency=medium

  * New upstream release.
  * Remove upstreamed patch.
    - 01_gallium-util-add-missing-u_debug-include.patch
  * Remove gallium-pipe, no longer built.

mesa (10.3.0~rc3-3) experimental; urgency=medium

  [ Andreas Boll ]
  * Bump llvm-3.5-dev and libclang-3.5-dev to 1:3.5-1, should fix FTBFS on
    kfreebsd-*.
  * Bump compat to v9 for changed dh_strip behavior:
    - dh_strip puts separated debug symbols in a location based on their
      build-id (Closes: #755921).
  * Drop redundant libegl1-mesa-drivers.install.linux.in.

  [ Dima Kogan ]
  * All -dev packages are now Multi-Arch: same (Closes: #689088, #678040).

  [ Julien Cristau ]
  * Upload clean source without partial Ubuntu alternatives patches (closes: #761678)

mesa (10.3.0~rc3-2) experimental; urgency=medium

  [ Andreas Boll ]
  * Add 01_gallium-util-add-missing-u_debug-include.patch, fixes FTBFS on
    big endian archs.
  * Enable --with-egl-platforms=drm on kfreebsd-any, should fix FTBFS.
  * Don't try to install vdpau hardlinks on hurd, should fix FTBFS.

  [ Fabio Pedretti ]
  * debian/rules: minor cleanup.

mesa (10.3.0~rc3-1) experimental; urgency=medium

  [ Maarten Lankhorst ]
  * Build with llvm 3.5.
  * New upstream release.
  * Remove mention of tdfx.

  [ Timo Aaltonen ]
  * mesa-common-dev: Add glcorearb.h.
  * not-installed: Skip libglapi.so.
 -- Maarten Lankhorst <email address hidden> Mon, 29 Sep 2014 14:33:23 +0200

Changed in mesa (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.