Hello Zach,
Thanks for recent cleanup of daily Android builds. We are down to 19 daily builds from 30 we had a month ago. Still, I remember that in one of mails you said that you consider that it would be possible to cut number even further (7 or 10, I don't remember now). So, I wonder if it just takes long time to go thru builds and check which are daily and which are not.
So, below are the list of current recurring jobs for your review. Let me know if there any which can be turned off, and if I can help with that (for example, feel free to mark those in the response, and I'll make the change). Also, if it makes sense, we can use lower frequency for some of builds, actually, we've been doing that for linaro-android_toolchain-4.5-bzr for a while (builds twice a week).
I guess, it makes sense to do such review regularly, for example, once a month. Infra team now has tools to query the regular builds easily, so hopefully we can keep daily builds under close control now.
Thanks, Paul
linaro-android_imx53-ics-gcc47-freescalelt-stable-open linaro-android_imx6-ics-gcc47-freescalelt-stable-open linaro-android_origen-ics-gcc47-samsunglt-stable-blob linaro-android_origen-ics-gcc47-samsunglt-tracking-blob linaro-android_panda-ics-gcc44-kwg-upstream-open linaro-android_panda-ics-gcc47-tilt-stable-blob linaro-android_panda-ics-gcc47-tilt-tracking-blob linaro-android_panda-master-gcc44-aosp-stable-blob linaro-android-restricted_vexpress-rtsm-isw-ics-gcc46-armlt-stable-open linaro-android-restricted_vexpress-rtsm-isw-ics-gcc47-armlt-stable-open linaro-android_snowball-ics-gcc46-igloo-stable-blob linaro-android_snowball-ics-gcc46-igloo-tracking-blob linaro-android_snowball-ics-gcc47-igloo-tracking-blob linaro-android_toolchain-4.5-bzr linaro-android_toolchain-4.6-bzr linaro-android_toolchain-4.7-bzr linaro-android_toolchain-trunk linaro-android_vexpress-ics-gcc47-armlt-tracking-open linaro-android_vexpress-rtsm-ics-gcc47-armlt-stable-open
Hi,
On 14 May 2012 14:11, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
linaro-android_imx53-ics-gcc47-freescalelt-stable-open linaro-android_imx6-ics-gcc47-freescalelt-stable-open linaro-android_origen-ics-gcc47-samsunglt-stable-blob linaro-android_origen-ics-gcc47-samsunglt-tracking-blob linaro-android_panda-ics-gcc44-kwg-upstream-open linaro-android_panda-ics-gcc47-tilt-stable-blob linaro-android_panda-ics-gcc47-tilt-tracking-blob linaro-android_panda-master-gcc44-aosp-stable-blob linaro-android-restricted_vexpress-rtsm-isw-ics-gcc46-armlt-stable-open linaro-android-restricted_vexpress-rtsm-isw-ics-gcc47-armlt-stable-open linaro-android_snowball-ics-gcc46-igloo-stable-blob linaro-android_snowball-ics-gcc46-igloo-tracking-blob linaro-android_snowball-ics-gcc47-igloo-tracking-blob linaro-android_vexpress-ics-gcc47-armlt-tracking-open linaro-android_vexpress-rtsm-ics-gcc47-armlt-stable-open
For all of those, I think it would be great to have a "if anything changed" switch -- check out the manifest, compare the checksums to those of the latest build, and if they all match and the compiler hasn't changed, don't do the build.
linaro-android_toolchain-4.5-bzr
The frequency of this can probably be reduced even more. I don't think we'll be making any more 4.5 based releases unless some really serious issue shows up.
linaro-android_toolchain-4.6-bzr
Given we've pretty much moved on to 4.7, I'd be ok with reducing the frequency of this one.
linaro-android_toolchain-4.7-bzr linaro-android_toolchain-trunk
Those should definitely stay (maybe also with a "only if anything changed" condition - but it's probably harder to do there given they pull in stuff from places not listed in the manifest.
ttyl bero
Hello Bernhard,
On Mon, 14 May 2012 14:40:36 +0200 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
Hi,
On 14 May 2012 14:11, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
linaro-android_imx53-ics-gcc47-freescalelt-stable-open linaro-android_imx6-ics-gcc47-freescalelt-stable-open linaro-android_origen-ics-gcc47-samsunglt-stable-blob linaro-android_origen-ics-gcc47-samsunglt-tracking-blob linaro-android_panda-ics-gcc44-kwg-upstream-open linaro-android_panda-ics-gcc47-tilt-stable-blob linaro-android_panda-ics-gcc47-tilt-tracking-blob linaro-android_panda-master-gcc44-aosp-stable-blob linaro-android-restricted_vexpress-rtsm-isw-ics-gcc46-armlt-stable-open linaro-android-restricted_vexpress-rtsm-isw-ics-gcc47-armlt-stable-open linaro-android_snowball-ics-gcc46-igloo-stable-blob linaro-android_snowball-ics-gcc46-igloo-tracking-blob linaro-android_snowball-ics-gcc47-igloo-tracking-blob linaro-android_vexpress-ics-gcc47-armlt-tracking-open linaro-android_vexpress-rtsm-ics-gcc47-armlt-stable-open
For all of those, I think it would be great to have a "if anything changed" switch -- check out the manifest, compare the checksums to those of the latest build, and if they all match and the compiler hasn't changed, don't do the build.
Yes, that was raised couple of times, but so far we don't have machinery for that. Nor it's really that easy. For manifests which don't have tags/SHAs, it should check actual underlying repos. Then there's non-git repos, like toolchain builds you mention below. Then we want advanced trigger logic - "build daily if there were any changes" (to start unconditionally and check for updates as part of build already wastes 1 machine-hour). Then we should see how this fits/interacts with pre-merge test builds from Gerrit changes (which we kinda have but which grew unmaintained, I wonder if people remember about them). So, instead of trying partial quick hacks, we'd better think how to get full-feature, flexible and reliable system. Hopefully, something to discuss at Connect.
linaro-android_toolchain-4.5-bzr
The frequency of this can probably be reduced even more. I don't think we'll be making any more 4.5 based releases unless some really serious issue shows up.
linaro-android_toolchain-4.6-bzr
Given we've pretty much moved on to 4.7, I'd be ok with reducing the frequency of this one.
Sounds good on these 2, I'll go for that, unless concerns will be raised.
linaro-android_toolchain-4.7-bzr linaro-android_toolchain-trunk
Those should definitely stay (maybe also with a "only if anything changed" condition - but it's probably harder to do there given they pull in stuff from places not listed in the manifest.
ttyl bero
Hello,
On Mon, 14 May 2012 14:40:36 +0200 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
[]
linaro-android_toolchain-4.5-bzr
The frequency of this can probably be reduced even more. I don't think we'll be making any more 4.5 based releases unless some really serious issue shows up.
Ok, set to build weekly (on Fri).
linaro-android_toolchain-4.6-bzr
Given we've pretty much moved on to 4.7, I'd be ok with reducing the frequency of this one.
Set to build twice a week, Wed/Fri.
Hello Zach:
On 14 May 2012 08:11, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
-- snip --
linaro-android_snowball-ics-gcc46-igloo-tracking-blob
We should get rid of this one
anmar
On 14 May 2012 16:15, anmar.oueja@linaro.org anmar.oueja@linaro.org wrote:
Hello Zach:
On 14 May 2012 08:11, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
-- snip --
linaro-android_snowball-ics-gcc46-igloo-tracking-blob
We should get rid of this one
So far, previous 12.05 release candidate have used this build. I've been notified today that finally Snowball has switched to GCC 4.7. We'll get rid of gcc46 build as soon as we're confident that we can release gcc47 build for 12.05 release.
Cheers,
Fathi
On 12-05-14 08:04 AM, Fathi Boudra wrote:
On 14 May 2012 16:15, anmar.oueja@linaro.org anmar.oueja@linaro.org wrote:
Hello Zach:
On 14 May 2012 08:11, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
-- snip --
linaro-android_snowball-ics-gcc46-igloo-tracking-blob
We should get rid of this one
So far, previous 12.05 release candidate have used this build. I've been notified today that finally Snowball has switched to GCC 4.7. We'll get rid of gcc46 build as soon as we're confident that we can release gcc47 build for 12.05 release.
As I have discussed this with a few people - I personally don't think it is advisable to build android with gcc 4.7 and load MM and mali libs built with gcc 4.6.
The build does come up and seems to work fine but I'm sure it won't be long before we start seeing weird behaviour and loose countless amount of hours debugging problems that don't exist.
For 12.05 I suggest we stick to gcc 4.6 for snowball. Going from 4.0.3 to 4.0.4 is a good idea but mixing 4.6 with 4.7 doesn't sound right to me.
Mathieu.
Cheers,
Fathi
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-android@lists.linaro.org
-
anmar.oueja＠linaro.org -
Bernhard Rosenkränzer -
Fathi Boudra -
Mathieu Poirier -
Paul Sokolovsky