This bug was fixed in the package mesa - 10.0.1-1ubuntu2
---
mesa (10.0.1-1ubuntu2) trusty; urgency=medium
[ Matthias Klose ]
* Build using llvm-3.4.
-- Maarten Lankhorst maarten.lankho...@ubuntu.com Thu, 19 Dec 2013
19:21:03 +0100
** Changed in: mesa (Ubuntu)
Status:
** Branch linked: lp:ubuntu/trusty-proposed/mesa
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1260068
Title:
Unity continuous-integration fails in armhf due possibly to a libegl
issue
To
I would prefer not to revert it for now, but instead fix the bug. I've
made a trusty chroot for testing on my pandaboard, how do I run those
tests myself?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
To build Unity and run the tests in an up-to-date Trusty build
environment you need to use the GTK fix branch (API changes in GTK
prevent Unity from building using trunk).
# apt-get build-dep unity
# bzr branch lp:~townsend/unity/fix-gtk-build-error/
# cd fix-gtk-build-error
# dpkg-buildpackage
I'm quite certain that this is not a Unity issue as completely separate
merge proposals all fail armhf CI. However, we don't have definitive
proof of that, so we are trying other ways to debug this.
We tried the LIBGL_ALWAYS_SOFTWARE=1 env var in an amd64 build, but no
where in the log does it
Unity built and passed all tests on armhf with the reconfigured Mesa
from the PPA.
http://s-jenkins.ubuntu-ci:8080/job/unity-trusty-armhf-ci/61/consoleFull
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
For reference, the reconfigured Mesa is just reverting this change:
http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/trusty/mesa/trusty/revision/206/debian/rules
** Changed in: mesa (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a
Yeah but that can fail for any number of reasons, even things in unity.
Can you confirm this on x86 with LIBGL_ALWAYS_SOFTWARE=1 set in the
environment? That should force a fallback on llvmpipe.
** Changed in: mesa (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug
** Tags added: ci-engineering
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1260068
Title:
Unity continuous-integration fails in armhf due possibly to a libegl
issue
To manage notifications
Do you have a log of the last passing test then?
** Changed in: mesa (Ubuntu)
Status: New = Incomplete
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Sure do: https://jenkins.qa.ubuntu.com/job/unity-trusty-armhf-
autolanding/40/consoleFull
This was on Dec. 9 which had Mesa version 9.2.2-1ubuntu2.
** Changed in: mesa (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
11 matches
Mail list logo
