From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177]) by dpdk.org (Postfix) with ESMTP id D3A1EB426 for ; Thu, 25 Sep 2014 16:59:07 +0200 (CEST) Received: by mail-we0-f177.google.com with SMTP id t60so7987698wes.8 for ; Thu, 25 Sep 2014 08:05:25 -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=eEVi9yQWK/8EtqPn/HDsxOKPC9sHPQXStgV4+OQf194=; b=WyynTWvau9S/TQWW2Ytcr7+sjazQQM3LuLM565lQjK3053K5mkl2ypXFE29fLIq+7T 2NU1gbJ2jEWC+k4Uk2YnoNuivd5PLnEfc1Y7H/Na1c/BA+oFe7olO9XikKSqPnvaDi9x USIN+MqJHg1U2fPtHJZFJGIKXJ9FfmgamlXM3I6fLGlddYLudCPbX29YQFzp2Q/8iL3Y QoNqZHdxvNQNIcexahhjAhvvZjnuYtny+LOQe5+po9SIqkrOw/BetJ7S9nEBSJBlR4Ez Meo3L4I55Z60FnvY6g6X3uuJW6hZPW3cgJQRCU8o1Z7BEVFE+k2gondgsP5INr0yMyH8 T8aA== X-Gm-Message-State: ALoCoQmQreJz7lBMR+T+8hbkdB/F3O4vWz08dNDJAdKoN0YFT3mZW6dXPesVBbSqEeXC87kYQmcz X-Received: by 10.180.100.37 with SMTP id ev5mr38826386wib.49.1411657525813; Thu, 25 Sep 2014 08:05:25 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id gl10sm2567284wib.1.2014.09.25.08.05.24 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Sep 2014 08:05:24 -0700 (PDT) From: Thomas Monjalon To: "Cao, Waterman" Date: Thu, 25 Sep 2014 17:05:16 +0200 Message-ID: <1636341.y1s87QthrV@xps13> Organization: 6WIND User-Agent: KMail/4.13.3 (Linux/3.15.8-1-ARCH; KDE/4.13.3; x86_64; ; ) In-Reply-To: References: <1411037752-8000-1-git-send-email-bruce.richardson@intel.com> <4239709.GvnD5XaY1L@xps13> 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: Thu, 25 Sep 2014 14:59:08 -0000 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. We could write some guidelines for test and bug reports and publish it on the website. Drafts are welcome. Thanks -- Thomas