Hi Hannu On 04/15/2012 12:26 PM, Hannu Nyman wrote: > During the long pause in buildbot snapshots last month I got interested > in the snapshot builds. > > I noticed that some of the platforms are being built daily although they > have not completed the build process successfully for 1-2 years, in some > cases never. It seems like a waste of CPU power and other resources to > continue compiling those platforms daily. The platforms should either be > fixed or their daily builds abandoned. > > Most of the failures seem to be missing kernel config symbols, and those > don't get automagically fixed. > > > Below is a short summary of the 35 buildbot snapshot platforms: > > 24 platforms with daily builds ok during last week: > adm5120, ar7, ar71xx, atheros, au1000, brcm47xx, brcm63xx, cobalt, > ep93xx, etrax, gemini, ixp4xx, kirkwood, lantiq, mpc52xx, octeon, orion, > ppc40x, ppc44x, ramips, sibyte, uml, x86, xburst > > 2 abandoned platforms, no builds done (which is also ok): > olpc 24-Oct-2009, goldfish 10-Mar-2010
There are probably more platforms not being build by the buildbot at all. > 3 recent failures (in February 2012): > iop32x 9-Feb-2012 looks like a platform-specific error > rb532 12-Feb-2012 gcc version change: cc1: all warnings being treated > as errors > rdc 27-Feb-2012 kernel config symbols missing This is normal and happens because the developers do not monitor the buildbot builds daily. I hope some developer will fix these or someone sends a patch to fix these problems to the mailing list. > 4 ancient failures (2010 - July 2011): > at91 20-Mar-2011 kernel config symbols missing > avr32 1-Jul-2011 kernel config symbols missing > pxcab 4-Nov-2010 kernel config symbols missing > s3c24xx 13-Feb-2011 kernel config symbols missing These targets are looking unmaintained to me. The missing kernel config symbols are probably not the only problems these targets have. It would be nice if someone from the community would work on these targets and sends patches and also runtime test them. It could also be that the "kernel config symbols missing" error just hides other problems. > 2 Never: > These have never completed a build succesfully, or at least it has not > been uploaded to the snapshot server: > ps3 kernel config symbols missing > ubicom32 ERROR: Missing site config for target > "ubicom32-openwrt-linux-uclibc" These targets are really unmaintained and making ubicom32 work nicely is hard work. > Developers might consider abandoning the daily builds of those ancient > failures, or maybe spend a few hours fixing the missing kernel config > symbols. It serves no purpose that buildbots crunch those platforms > daily, just to fail. > > I made a patch for at91, but have not tested it any further in addition > to compiling the kernel. > https://lists.openwrt.org/pipermail/openwrt-devel/2012-April/014897.html I did not had a closer look into the commit and the other documentation about the targets if some of the things I said are wrong, please correct me. The OpenWrt core developers are lacing man power, we do not have the time to maintain all platforms (~52) in the same quality. So if you or someone else wants to maintain some of the platforms none cares about it will be nice to see some patches for them. Hauke _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
