From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id C5A6211F5 for ; Fri, 26 Sep 2014 01:23:26 +0200 (CEST) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by fmsmga101.fm.intel.com with ESMTP; 25 Sep 2014 16:29:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,600,1406617200"; d="scan'208";a="480072948" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by azsmga001.ch.intel.com with ESMTP; 25 Sep 2014 16:29:42 -0700 Received: from irsmsx107.ger.corp.intel.com (163.33.3.99) by IRSMSX101.ger.corp.intel.com (163.33.3.153) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 26 Sep 2014 00:29:41 +0100 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.248]) by IRSMSX107.ger.corp.intel.com ([169.254.10.68]) with mapi id 14.03.0195.001; Fri, 26 Sep 2014 00:29:41 +0100 From: "Ananyev, Konstantin" To: Thomas Monjalon , "Cao, Waterman" Thread-Topic: [dpdk-dev] patches validation Thread-Index: AQHP2NI1lk7HwqKfPEygTK2S/uyzBZwSfijg Date: Thu, 25 Sep 2014 23:29:41 +0000 Message-ID: <2601191342CEEE43887BDE71AB9772582137AB66@IRSMSX104.ger.corp.intel.com> References: <1411037752-8000-1-git-send-email-bruce.richardson@intel.com> <4239709.GvnD5XaY1L@xps13> <1636341.y1s87QthrV@xps13> In-Reply-To: <1636341.y1s87QthrV@xps13> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] patches validation 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, 25 Sep 2014 23:23:27 -0000 > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Thursday, September 25, 2014 4:05 PM > To: Cao, Waterman > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] patches validation >=20 > 2014-09-25 13:07, Cao, Waterman: > > I will work with team to see if we can improve test report. > > Because intel validation team will continue to upgrade test cases to v= erify feature, > > I think that it's still worth to verify patch or features even it has = already integrated branch. >=20 > Of course, it's important to continue validation after integration. > But please do not send test report on the list for patches which are > already integrated, except for 2 cases: > 1) there is an error > 2) this is a new feature and you want to explain how to test it > (btw, how do you test "zero copy" and "one copy" for virtio?) >=20 > About report content, please add these informations: > - commit id or tag used as a base to apply the patch > - tools used for the test (testpmd, sample, qemu, etc) > - command parameters if relevant > - test topology if relevant >=20 > If someone think about an useful information I missed, please share it. May be it is just me, but what's wrong with mail for every tested patch? At least it makes easy to check was the patch formally validated or not - a= ll you have to do - grep through mail archives. Konstantin > We could write some guidelines for test and bug reports and publish it > on the website. Drafts are welcome. >=20 > Thanks > -- > Thomas