From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 7C7CA5A50 for ; Thu, 29 Oct 2015 16:19:57 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga103.fm.intel.com with ESMTP; 29 Oct 2015 08:19:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,214,1444719600"; d="scan'208,217";a="838501611" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga002.fm.intel.com with ESMTP; 29 Oct 2015 08:19:41 -0700 Received: from fmsmsx114.amr.corp.intel.com (10.18.116.8) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 29 Oct 2015 08:19:41 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX114.amr.corp.intel.com (10.18.116.8) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 29 Oct 2015 08:19:40 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.204]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.47]) with mapi id 14.03.0248.002; Thu, 29 Oct 2015 23:19:38 +0800 From: "Liu, Yong" To: "dev@dpdk.org" Thread-Topic: dpdk pre-patch testing introduction Thread-Index: AdESXTIe0I95ydrcSzmZlO4LKW6XIw== Date: Thu, 29 Oct 2015 15:19:38 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10F379B0@SHSMSX103.ccr.corp.intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] dpdk pre-patch testing introduction X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2015 15:19:58 -0000 Dear all, Our validation team is working on pre-patch testing to support contiguous i= ntegration in DPDK community. I'd like to share the latest status and some details of our solution to you= . The main target of pre-patch testing is supplement the health of each patc= h set as soon as possible. It will help both submitter and maintainer to know the status of patch set = before it's merged. Some of you have received the email which was generated by this tool. Let m= e introduce it to you. Example email subject: |SUCCESS| pw 8162 ixgbe: remove useless fields in tx_offload on TCP che= cksum request The first item is the overall status of this patch set. The second item= is the patchwork ID and its commit log. There are 4 status to report as the following: Malformed patch: Patch's format doesn't incorrect, not applied in lates= t branch SUCCESS : Pass all testing. ERROR : fail in some testing, error information can be found in repor= t Not run : Failed to compile, not able to perform functional testing Email content included more detailed information of this patch set, like bu= ild failure log and failed cases log. If patch set modified files for document, the content will also include the= status of "Doc Compilation". 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. Currently the patch testing only run unit test and basic function test on t= his 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 tes= ter and perform specific testing on it. Since platform limitation, we are not able to verify regression test on oth= er NIC, Linux kernel. We plan to add more platforms and support different NIC and kernels in the = future. Best regards, DPDK validation team