Hello Bernhard,

On Thu, 28 Jul 2011 22:34:25 +0200 Bernhard Rosenkranzer bernhard.rosenkranzer@linaro.org wrote:

On 28 July 2011 21:37, Angus Ainslie angus.ainslie@linaro.org wrote:

...

I have a android manifest that builds fine on my local build server with -j4 for concurrent makes.

Have you tried doing a re-download locally? The issue I've had that resulted in the same error (while it may not be elfcopy for you) was simply that a download failed - it didn't show up locally because I had it checked out, and apparently download errors don't show up in the build server's logs.

Seconding James' request, can you elaborate/submit bug for such case? Do you mean exactly download or checkout here? Source checkout for sure leads to error and build failure, and as for downloads, I had cases when curl which was used in few places swallowed protocol errors (like, when it got 404 it just downloaded error payload page and exited with 0 status). In places I hit that I replaces it with wget, maybe more complete code audit should be performed.

In either way, one of big android-build's is to avoid "false positives", i.e. avoid building something not updated or not properly downloaded. We run all build setup scripts with "set -e", so any error with that execution immediately leads to build failure. So again, if you faced any issue when some error was swallowed, please report it.

I doubt the parallel build is the issue, given the other builds are pretty much doing the same thing and they tend to succeed.

ttyl bero

...

The same manifest fails to build on android-build.linaro.org The log is here

https://android-build.linaro.org/jenkins/job/angus-akkea_smdkv310/6/consoleT...

Is there something I can add to the build variables  to disable the concurrent make ? This would be just to debug the manifest file and then re-enable it afterwards

Thanks Angus

-- Angus Ainslie angus.ainslie@linaro.org Team Lead, Samsung Landing Team

---

linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev

---

linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev

On Thu, Jul 28, 2011 at 11:09 PM, James Westby james.westby@canonical.com wrote:

On Thu, 28 Jul 2011 13:37:38 -0600, Angus Ainslie angus.ainslie@linaro.org wrote:

...

I have a android manifest that builds fine on my local build server with -j4 for concurrent makes.

The same manifest fails to build on android-build.linaro.org The log is here

https://android-build.linaro.org/jenkins/job/angus-akkea_smdkv310/6/consoleT...

Is there something I can add to the build variables  to disable the concurrent make ? This would be just to debug the manifest file and then re-enable it afterwards

You can put

MAKE_JOBS=1

yep, just want to point out that we don't need that for any android platform build so far, so I don't think that this is really the issue. Anyway, if it helps for debugging, go for it!

On Fri, 29 Jul 2011 13:10:48 -0600, Angus Ainslie angus.ainslie@linaro.org wrote:

On Thu, Jul 28, 2011 at 3:09 PM, James Westby james.westby@canonical.com wrote:

...

On Thu, 28 Jul 2011 13:37:38 -0600, Angus Ainslie angus.ainslie@linaro.org wrote:

...

I have a android manifest that builds fine on my local build server with -j4 for concurrent makes.

The same manifest fails to build on android-build.linaro.org The log is here

https://android-build.linaro.org/jenkins/job/angus-akkea_smdkv310/6/consoleT...

Is there something I can add to the build variables  to disable the concurrent make ? This would be just to debug the manifest file and then re-enable it afterwards

You can put

MAKE_JOBS=1

I don't suppose there is a MAKE_TARGETS to go along with this is there ?

There is indeed.

What is the default make command ?

Per http://bazaar.launchpad.net/~linaro-infrastructure/linaro-android-build-tool... it is "boottarball systemtarball userdatatarball".

Cheers, mwh