Re: [riot-devel] Helping out with the CI situation

2016-03-06 Thread Kaspar Schleiser
Hey, let me clarify: On 03/06/2016 02:34 PM, Kaspar Schleiser wrote: > the current build system is horribly inefficient ... for parrallel builds, as it wasn't designed that way. Kaspar ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/

Re: [riot-devel] Helping out with the CI situation

2016-03-06 Thread Kaspar Schleiser
Hey, On 03/06/2016 05:28 AM, Adam Hunt wrote: > With all the chatter about the CI situation lately I got to wondering if > there might be some way I could help out. It sound like Kaspar has > things under control with the new CI system but what about builders; are > there enough CPU cycles availab

Re: [riot-devel] Helping out with the CI situation

2016-03-06 Thread DipSwitch
I had the same idea. :) The latest was that small package changes take about 5 min to complete. If there are changes in the kernel there is a CCACHE huge mismatch and it takes about 30 minutes. On 6 Mar 2016 05:29, "Adam Hunt" wrote: > With all the chatter about the CI situation lately I got to w

[riot-devel] Helping out with the CI situation

2016-03-05 Thread Adam Hunt
With all the chatter about the CI situation lately I got to wondering if there might be some way I could help out. It sound like Kaspar has things under control with the new CI system but what about builders; are there enough CPU cycles available for the current rate of RIOT development, what about