From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 00/17] Support ARMv7 architecture Date: Thu, 29 Oct 2015 15:02:03 +0100 Message-ID: <2039554.9Hm8ZoiZzc@xps13> References: <1445877458-31052-1-git-send-email-viktorin@rehivetech.com> <20151028183837.5612029d@jvn> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Jan Viktorin Return-path: Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by dpdk.org (Postfix) with ESMTP id 96B6211F5 for ; Thu, 29 Oct 2015 15:03:14 +0100 (CET) Received: by wmff134 with SMTP id f134so25535791wmf.0 for ; Thu, 29 Oct 2015 07:03:14 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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. The most basic test is the compilation, then there are some unit tests and DTS. Are you OK to start with a basic daily compilation test? It can be achieved with a simple crontab job. 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.