Paul Eggleton wrote: > We do definitely want automated testing on real hardware; it's just that > that it presents a number of problems that need solving: > > * How do you deploy the image/kernel/bootloader onto the board in an > automated manner? To different kinds of boards? > * How do you manage access to the boards when you have multiple > autobuilders potentially wanting to make use of them at around the same > time?
These are all solved problems. We build and auto-test Yocto nightly on a bunch of different hardware using tftp and nfs. I'm sure other teams do something similar. However, since there is no Yocto standard for this yet we all do it slightly differently. Also, even when/if Intel sets up an automated hardware lab for Yocto, it will necessarily only have a limited selection of boards. Perhaps we could have a system where we pool community test results into one place rather than depend on a single test lab. I have said it before, and I'll remind/nag about it again: Please don't run off and do this on your own. This is something that touches the daily work of many community members and it should be done with open discussion. -- Björn _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
