From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by dpdk.org (Postfix) with ESMTP id 1BEF01B49F for ; Fri, 4 Jan 2019 16:34:08 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id E7FBD14D0; Fri, 4 Jan 2019 10:34:06 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 04 Jan 2019 10:34:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=xcfABOmF/6xQ3+tznUn0VK5Wpsgqav/Rkt1zlKjZLu4=; b=sxdaBMm2Bd3D wJiaakwRm5wZ/sGRDpuH3TQt1aIi4WAe8ZGBtSvfCZDDgsDJrGa18O93/lxc/6nP rDCyArK2rbJriE9BY6ZnMnl0jw9mEhKNTnQzQcw0PwKN2OJG1F968FeBUMaztCE7 pbgly0mSAVBwGjbwpckQfPvLXkFFBI0= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=xcfABOmF/6xQ3+tznUn0VK5Wpsgqav/Rkt1zlKjZL u4=; b=sDHVmCddl0UE2IPNzQmaMNFZWlAqUmFlqLouylBoaQER3kG45XhVhV5XK eyGqg7a7zeuasffvun3+Q2bCaLgeS9RPed5LaB4vp3yU2jdYR2TA6y8OhvCMiB50 OhLxgnNwI7TChoLq6flndj/pXwKWAcWH1OxQkpfkSzRCjmSVyNDvL8ZkqIgcrWHr tgk4k6GRXNfU0QZb0+gSyUBr/dHYofArroMLgPzT9BoHYMrbBuVmnECHM5dXjUi/ J7IhfnM1c14I5D28t02/sZurbFn0sWmJLf4PYMKj69yIYYU9euq71MEB5r6IzVCI mKbqRtFMEhpiqfymQyBKvnPQ/a4kA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrvddugdektdculddtuddrgedtkedrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtne cuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 4535E100E5; Fri, 4 Jan 2019 10:34:05 -0500 (EST) From: Thomas Monjalon To: Jeremy Plsek Cc: ci@dpdk.org, Rami Rosen Date: Fri, 04 Jan 2019 16:34:03 +0100 Message-ID: <2631230.hnArF6gTu5@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-ci] Question about performance test X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2019 15:34:08 -0000 04/01/2019 15:44, Jeremy Plsek: > Hi Rami, > > I'm the current maintainer of the DPDK Performance CI. I realize that the > performance results don't point to the website, so it's not obvious on > where to find this information. You can find an overview of these tests > here: https://lab.dpdk.org > > Most of this information can be either found on the detailed results of a > test (such as https://lab.dpdk.org/results/dashboard/patchsets/4157/) or on > the about page (https://lab.dpdk.org/results/dashboard/about/). Do you plan to add such URL in the report sent to patchwork? > We don't apply the doc folder when applying the series, in case a patch > included code unrelated to documentation. If others in the group feel that > it's still unnecessary to include "doc" labeled series, I can look into > filtering them out. Instead of filtering based on the label, you could filter based on the paths of modified files. Note that such filter depends on the test you run, because you could also test the doc syntax in the CI.