Subject: Mir's building. And Mir's not building.

From: Daniel van Vugt <[email-masked]>
Date: Tue, 18 Aug 2015 17:15:38 +0800

The wily archive transition is now complete and you probably noticed you 
can once again build lp:mir on a fully updated wily system.

However, the transition has left a few things broken that need our 
attention:

* Cross compile scripts don't work.
   Solution: 
https://code.launchpad.net/~vanvugt/mir/dual-cross-compile/+merge/268299

* New test case failures in CI - fd leaks?
   alan_g is looking into it.

* Clang builds fail, including in CI.
   No one owns this yet.

* Mako deployment fails in CI:
   alan_g has asked fginther. Not heard back.

* Any other issues?

- Daniel

---

From: Alan Griffiths <[email-masked]>
Date: Tue, 18 Aug 2015 10:21:40 +0100

One further data point: The test failures are reproducible with -r2834 -
which eliminates the changes we landed while CI was broken by the
archive transition.

On 18/08/15 10:15, Daniel van Vugt wrote:
> The wily archive transition is now complete and you probably noticed
> you can once again build lp:mir on a fully updated wily system.
>

---

From: Alan Griffiths <[email-masked]>
Date: Tue, 18 Aug 2015 13:09:24 +0100

>   alan_g is looking into it.

Solutions:

https://code.launchpad.net/~alan-griffiths/mir/fix-CI-test-failure/+merge/268305
   
https://code.launchpad.net/~alan-griffiths/mir/fix-more-CI-test-failure/+merge/268319

---

From: Alan Griffiths <[email-masked]>
Date: Tue, 18 Aug 2015 14:35:52 +0100

>> * Clang builds fail, including in CI.

Reproduced, investigating.

---

From: Alan Griffiths <[email-masked]>
Date: Tue, 18 Aug 2015 17:47:19 +0100

>>> you can once again build lp:mir on a fully updated wily system.
...
> Reproduced, investigating.

as best we can figure it clang++ is not sufficiently compatible with g++5 and in a way that we can't fix or workaround. https://llvm.org/bugs/show_bug.cgi?id=23529 summarises the reason: for some interfaces (std::string) g++ now uses an "abi_tag" that clang doesn't grok.

While that state remains we won't be able to build Mir with clang on
Wily.

We're planning to try switching the clang builds to run on Vivid.

---

From: Kevin DuBois <[email-masked]>
Date: Tue, 18 Aug 2015 14:05:45 -0400

As for the phone CI problem, it looks like there was a package transition
from "libprotobuf-lite9" in vivid to "libprotobuf-lite9v5" in wily. The job
is building on vivid, so the package depends on "libprotobuf-lite9". When
deployed on the wily phone image, the package resolver can't figure out
where to get "libprotobuf-lite9" (as its been renamed), and fails. The
solution is to build and deploy on the same system.

On Tue, Aug 18, 2015 at 12:47 PM, Alan Griffiths <
[email-masked]> wrote:

> as best we can figure it clang++ is not sufficiently compatible with g++5
> and in a way that we can't fix or workaround.
> https://llvm.org/bugs/show_bug.cgi?id=23529 summarises the reason: for
> some interfaces (std::string) g++ now uses an "abi_tag" that clang doesn't
> grok.
>
> --
> Mir-devel mailing list
> [email-masked]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/mir-devel
>

---

From: Alexandros Frantzis <[email-masked]>
Date: Wed, 19 Aug 2015 10:04:43 +0300

On Tue, Aug 18, 2015 at 05:47:19PM +0100, Alan Griffiths wrote:to 
> We're planning to try switching the clang builds to run on Vivid.

If we manage to fix the phone CI problem, which will then leave the
clang problem as the only CI blocker, I suggest that we disable clang
builds until the issue is resolved, so we can resume our normal CI
workflow as soon as possible. It's good to ensure that we have clang
support, but it's not essential and not worth blocking on.

Thanks,
Alexandros

---

From: Kevin DuBois <[email-masked]>
Date: Wed, 19 Aug 2015 14:11:03 -0400

With the phone CI, switching everything to vivid+overlay had a small
problem that was corrected in the test runner script (overlay was pinned
higher than the packages that were installed, leading to unresolvable
situations). Clang is running against vivid, and CI should be unblocked!