On Mon, May 06, 2013 at 09:41:22PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 21:29 Mon 06 May , Linus Walleij wrote: > > On Sun, May 5, 2013 at 10:22 PM, Jean-Christophe PLAGNIOL-VILLARD > > <plagnioj@xxxxxxxxxxxx> wrote: > > > > > I was thinking to put a jenkins to test Linus HEAD all the time > > > And with some automatic test one some hw > > > > > > to detect it more quick > > > > Hm yeah, I think I need a broader diversity of testsystems too ... I have this > > nice Chromebook so I thought if I could get a mainline kernel running on > > it I'd have a bigger coverage as well. > > Maybe we could all work together to setup such automatic testing tool > > I mean all vendors Don't bother. We had one, Simtec's Vince Sanders gave us the build side. No one was interested. No one took any notice of it. I have one for a limited number of platforms - it even boots the resulting kernels on real hardware. The only person who looks at it is me. Again, just one person, so little value. And that same thing will appy to anything else setup by anyone else. It's a good idea, but it only really works if people can be bothered to derive value from it by checking the results. My conclusion is that build and boot test systems just don't work in an open source environment as no one actively checks the results. Why would they - maintainers already have enough to do with reading 6500+ emails a month on mailing lists. Why bother going to look at a website as well which might give even more work. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
