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 say it's using llvmpipe for sure. The build and tests passed as they did before, so this is not a good test. Timo A. also suggested trying a test Mesa package reverting the arm llvmpipe support. We are in the middle of getting a PPA setup to get an armhf build and then try that. We'll report back once this is done. -- 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/1260068 Title: Unity continuous-integration fails in armhf due possibly to a libegl issue Status in “mesa” package in Ubuntu: Incomplete Bug description: Since mesa 10.0 has been released, our Unity continuous-integration tests are failing on armhf builds. This is a snippet of the log: libEGL warning: DRI2: failed to authenticate Segmentation fault (core dumped) The log can be found here for reference: https://jenkins.qa.ubuntu.com/view/Trusty/view/All/job/unity-trusty- armhf-ci/56/console I don't have the core file or have access to an armhf machine to reproduce, so I'm only going on evidence based on the warning and the timing of the issue. *Note* This is blocking automerging of Unity code, so this issue is pretty critical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1260068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
