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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1260068 Title: Unity continuous-integration fails in armhf due possibly to a libegl issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1260068/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
