From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: dpdk pre-patch testing introduction Date: Thu, 29 Oct 2015 17:30:37 +0100 Message-ID: <22607203.7fcSgJEPLE@xps13> References: <86228AFD5BCD8E4EBFD2B90117B5E81E10F379B0@SHSMSX103.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Liu, Yong" Return-path: Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by dpdk.org (Postfix) with ESMTP id 683728E81 for ; Thu, 29 Oct 2015 17:31:48 +0100 (CET) Received: by wicll6 with SMTP id ll6so232970772wic.0 for ; Thu, 29 Oct 2015 09:31:48 -0700 (PDT) In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E10F379B0@SHSMSX103.ccr.corp.intel.com> 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-29 15:19, Liu, Yong: > So far, we only enabled one platform to run automatic testing. > This platform installed Fedora 20 with Linux 3.18.9 and Intel Niantic NIC. Thanks for offering this service. > Currently the patch testing only run unit test and basic function test on this platform. > It can make sure that new patch doesn't break original code and functions. > Due to coverage limitation, it can't verify the functionality of new patch. > If you want to verify your patch's new function, you need to check with tester and perform specific testing on it. > > Since platform limitation, we are not able to verify regression test on other NIC, Linux kernel. > We plan to add more platforms and support different NIC and kernels in the future. The mailing list for test report is open to others. Submitters are white-listed. Feel free to contribute with your own tests on your own platform. Some work is ongoing to track the test results from patchwork. https://lists.ozlabs.org/pipermail/patchwork/2015-July/001363.html https://lists.ozlabs.org/pipermail/patchwork/2015-July/001369.html