From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by dpdk.org (Postfix) with ESMTP id DB4F97DEB for ; Fri, 26 Sep 2014 11:17:40 +0200 (CEST) Received: by mail-wg0-f44.google.com with SMTP id m15so877543wgh.15 for ; Fri, 26 Sep 2014 02:24:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=UJLS7p0yM+r/JbbFruX2t80l5dWh+333htiWV9Ao9U0=; b=CGIRMTHSVS5fZZp4YkG55cR4GjkFtdGYgSE/UbXl/r5bFBAajd4VGYTKUxv+c/fPRn HPSA771Oh97Eg+c+FsHOU+GCCFovDx9TEg/cZvs6aoVALQoJgiIEPekxgzBdMXdtwFKp tITYacVh5MC0cp88JjVKSNsuteWwZTZL2eRzwS3/vuxyP8PpVoGrd+fgstx+rzqPc9Kz RhHbtYK9G1bOhhOYw9AvDru3nfwfJBEDziqtQgm+RZHCL5ANwwSrcLLnYRvfCbQlD2dc StojoBwAv5MJK0TJUjH6SldnvNPCsDFDGb83ft9ldX03UvBwrbi5K2nWkgj/YG/jjSpW yOkQ== X-Gm-Message-State: ALoCoQmxpdyxsjPBAA88cxY+eeZDe23mFO22vOqJkVwICDKJUwOY1qLCfgSa/BXXqED9K18jNA/z X-Received: by 10.181.5.42 with SMTP id cj10mr1347867wid.28.1411723442406; Fri, 26 Sep 2014 02:24:02 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id i5sm5481259wjz.0.2014.09.26.02.24.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 Sep 2014 02:24:01 -0700 (PDT) From: Thomas Monjalon To: "Ananyev, Konstantin" Date: Fri, 26 Sep 2014 11:23:52 +0200 Message-ID: <2031841.CNMZT9rHpz@xps13> Organization: 6WIND User-Agent: KMail/4.13.3 (Linux/3.15.8-1-ARCH; KDE/4.13.3; x86_64; ; ) In-Reply-To: <2601191342CEEE43887BDE71AB9772582137AB66@IRSMSX104.ger.corp.intel.com> References: <1411037752-8000-1-git-send-email-bruce.richardson@intel.com> <1636341.y1s87QthrV@xps13> <2601191342CEEE43887BDE71AB9772582137AB66@IRSMSX104.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Fri, 26 Sep 2014 09:17:41 -0000 2014-09-25 23:29, Ananyev, Konstantin: > From: Thomas Monjalon > > 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 verify feature, > > > I think that it's still worth to verify patch or features even it has already integrated branch. > > > > 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?) > > > > 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 > > > > 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 > - all you have to do - grep through mail archives. The right place to check something about a patch is the git history. So it's important to send test reports before having it integrated in git. Doing so, without any reference to commit id, imply that the patch is pending. If you think it's really important to send test report about an integrated patch, the commit id must be clearly visible to quickly understand its status. There is something else wrong about these test reports: there is no useful information about how to reproduce the test. So it's not forbidden to send any email you want but please try to be more informative and easy to understand. We are getting a huge email traffic so everyone must be concerned about how to make it effective. Thanks -- Thomas