From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 339BBA046B for ; Thu, 27 Jun 2019 18:34:23 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A4DAB3798; Thu, 27 Jun 2019 18:34:22 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id C8A1F2C30; Thu, 27 Jun 2019 18:34:21 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6D4D6221BD; Thu, 27 Jun 2019 12:34:21 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 27 Jun 2019 12:34:21 -0400 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=z4jqmAwMnmGu4YK1AfVEhtBJjuQ3cIWQYlCfPIxhpik=; b=geqU9eOENYTz JRgUBMaK19R1CUEVeT4UTFg/yKZGscG8M+x8cZn9u+lz8q9FL7fPUfjOz3/DdXIY c0HfUxDsIzPDgHlsdPpPNsrLApxnevVOoGMxsyGp+ywKP+QB+mcjGjdohoFB70cn 2HaHjFBGRtoO7kyh2rcxgCkYRfNECe8= 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=fm3; bh=z4jqmAwMnmGu4YK1AfVEhtBJjuQ3cIWQYlCfPIxhp ik=; b=UZMKGdM2l3ykkyxmwfFwXj0ODRIksftizMME7no1KFpgTnfKVFNyldDwZ j/rwZkzHf5Bg0tlXt5NwH4Ldbb8trZVlqdExxILuEJkTFNNo8lgBkDW0Dwjf/coX xrafg/ty/uyIXc4XRuek463/KLY+Q8gYZDI5J8VUr+5SwTBpxCxCBMkr3zH9USfZ P8DoMleApQtOCNSRQjsT7Xk8vfi7r83wxjdceDvVAW8t7T/ZEfagwBeB+xgpGtem I3nIBtHgXeBybt4USlfj1AyYsZorOwJMQKaFzgFThxjUShRTNrqFpA13P26pjF1F 9K3/2ZPfp1CQoDf21k4kNmDvVydtQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudekgddutdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 F324680063; Thu, 27 Jun 2019 12:34:19 -0400 (EDT) From: Thomas Monjalon To: msantana@redhat.com, David Marchand , aconole@redhat.com Cc: dev@dpdk.org, ci@dpdk.org Date: Thu, 27 Jun 2019 18:34:18 +0200 Message-ID: <2134880.WhL1dmy7PZ@xps> In-Reply-To: <81c5f665-97ac-c4d0-8281-8f195c63195e@redhat.com> References: <1559638792-8608-1-git-send-email-david.marchand@redhat.com> <81c5f665-97ac-c4d0-8281-8f195c63195e@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-ci] [dpdk-dev] [PATCH 00/14] Unit tests fixes for CI 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: , Errors-To: ci-bounces@dpdk.org Sender: "ci" 04/06/2019 17:49, Michael Santana Francisco: > On 6/4/19 4:59 AM, David Marchand wrote: > > - the "perf" tests are taking way too long for my taste, > > We should still fix them. However I don't know if we should be running > the perf test for every job and every patch on travis. It takes too > long. The travis queue will be delayed too far behind for it to be of > any use. > > OTOH we could have one job as part of the travis build dedicated to > running tests (or just perf test). It's still time consuming but better > than running the test on every travis job. For this to work we would > need to decreased the timeout for the perf tests as the timeout for it > and the travis are both 10 minutes +Cc ci@dpdk.org I don't think we should run the perf tests in basic CI like Travis. We can run perf tests if the purpose is to compare the performance with previous releases, as some other tests in the community lab.