On Thu, 29 Oct 2015 15:02:03 +0100 Thomas Monjalon <thomas.monjalon at 6wind.com> wrote:
> 2015-10-28 18:58, David Marchand: > > > > - since you introduce a new architecture, do you intend to run daily > > > > build checks and send reports to the test-report mailing list ? > > > > > > I think, this is possible, if I automate it somehow. Do you mean to > > > test every individual patch? I have no tools for this (some ideas?). If > > > its just about git pull && test_script.sh, then it is quite OK. > > > > > > I'd appreciate some help, ideas, advices, experiences in this area... > > > > I am pretty sure Thomas has some ideas about this. > > In order to make sure new commits won't introduce a regression on ARM, > we need to run some tests before accepting the patch. > If those tests are not run, some daily tests could catch the recent > regressions. I understand the purpose. > The most basic test is the compilation, then there are some unit tests > and DTS. The unit tests are a problem at the moment. Probably, I will later find a way, how to perform some unit tests in QEMU. > > Are you OK to start with a basic daily compilation test? It can be achieved > with a simple crontab job. I can do daily build test in Jenkins or a cron job. Is it sufficient to check the master branch? Or you mean to pick patches from patchwork? That seems quite complicated to me. > If you or someone else have some time and a machine to do more, it would > be great. I'm sure the DPDK/ARM will gain enough interest to attract some > volunteers for more automatic tests. >