CI fails with error: invalid argument '/build/mir' to -fdebug-prefix-map

Magically fixed itself in the last few CI runs I've seen.

This appears to have been a short-lived flaw in CI itself.

Reopened due to a duplicate bug report.

And again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/2101/consoleFull

hmm, and another only 3 runs later:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/2104/console

Added tag 'testsfail'. Even though this is not a test failure, that's the tag everyone looks for with CI failures.

Again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2194/consoleFull

And again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/2220/console

This bug is getting more concerning.

yeah, we just hit it three times in a row with clang :/

Although this is still nowhere near the most common CI failure.

Is this one another that's specific to autolandings only?

And again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2300/console

Again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/2376/console

And today:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/2492/consoleFull

With clang again:

09:50:42 clang: error: invalid argument '/build/mir' to -fdebug-prefix-map

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2743/console

Again yesterday:

10:40:15 clang: error: invalid argument '/build/mir' to -fdebug-prefix-map

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2773/console

Again today:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2789/console

Today:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2802/console

And:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2806/console

Today:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/3017/consoleFull

Again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/3084/consoleFull

Again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/3309/console

Again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/3376/console

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=zesty/3560/console

Again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=zesty/3591/consoleFull

Again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/3657/consoleFull

tried reproducing the issue locally using both dh_auto_build and sbuild for a bit today, no luck. It seems to be an issue with parallelism and the build system, from the logs.

Indeed it would not be the first parallelism bug. Those are generally solved by adding missing dependencies in the CMakeLists. But I'd already had that thought and also failed to reproduce this bug...

And again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=zesty/3711/console

And another:
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/3751/console

And again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=zesty/3759/console

Again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/3801/console

Again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/3818/consoleFull

Also happening in the silos and wasting many hours of time

https://launchpadlibrarian.net/305634494/buildlog_ubuntu-zesty-amd64.mir_0.26.1+17.04.20170208.1-0ubuntu1_BUILDING.txt.gz

Again here:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/3953/console

Yes, this bug happens much more in autolanding than in regular CI.

Syncing task from Mir.