I'll add myself in a week or so. Need to see how I can get this organized. Wrt the wiki page I'd day remove the last succesful build column (or add a new one). The new column should mention the last build. In yet another column we can then add the reason.
E.g. currently khem has a ppc qemu thing where it says " fails to build sed ". Next tuesday it will be unclear if this is from last monday's tree or this monday's tree. Also i would suggest that everyone who participates builds with tinderbox enabled, and (at least in case of failure) adds a link to the tinderbox log. And one more question: The wiki pages says: "All volunteers start clean builds for the combinations they test," I have some platforms that are quite identical (eg sheevaplug and openrd; both marvell/kirkwood based). I have no problems testing for both, but as they are both armv5 and use the same soc, compiler etc, I kinda feel this as a waste of time. I think I would prefer it to do e.g. a bake for sheeva, followed by one for openrd (without a clean inbetween) to verify that the openrd specifics (probably only u-boot and kernel) work. I can imagine for the various omap3530 variants (beagle, overo, ...) this is also the case. (thinking of it, if cpu cycles/time an issue we could decide to pull some packages (e.g. some of the native ones) from pstage) Frans _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
