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 BC6B9A053A for ; Thu, 23 Jan 2020 16:59:11 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 91DDE2956; Thu, 23 Jan 2020 16:59:11 +0100 (CET) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 48B6B27D for ; Thu, 23 Jan 2020 16:59:10 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id EC6DE51C; Thu, 23 Jan 2020 10:59:08 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 23 Jan 2020 10:59:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding:content-type; s=mesmtp; bh=ZSA+hqlylz YpJcXemRWFe+Kzh69Bza+hD/2QcpVlex0=; b=eqHA0uDWxQBQiURHXFkZ+gziuz BLKFDLvMTKgQHG/9wqswdU38cPvez5VoTxKEIJ+Cajp+l+U/j1dk6NlYIzjGlN+P TY3jmhjlczTAirs6ZQAuxsZkHyhbKJHF+1sOpaS4Mr+rdMr3cJ0EcWiB6CzwlJyk ACMHpAdKzIvYkdKfo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=ZSA+hq lylzYpJcXemRWFe+Kzh69Bza+hD/2QcpVlex0=; b=eMDAwuvydeWCa0pmKLeRgB 8S9w7GTgqE5qG50g0Wy8U4dH5HqEFiqmQGow8UjRhCMJ9ObKRLoNOw+z8gEaSiHT PuFQT7AKZhMfi0wMNzWpCuRmu0qASmt4iVnxsz7rSf2Z294YtiM9n9ZWffy7wfho rGBhW/cHXt7hgaGFEJuKgHcHskC3jLaSkfAo0APxqYhMbfNtwg0HSVk+v6KZ95B6 vnDwgDmnLRO8UWeOmMXvwdIOxC7xBlGt80n3Ib+I6oMOCqaqHPwFEItX8NFEKkGu DgKsLO29guwEM1YrUfxfKCmqtyJGEENBAjmlzB5CBN6CUzKXS93Xy4y5NykaltgQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrvddvgdehudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgggfgtsehtufertddttd dvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhn jhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhho nhhjrghlohhnrdhnvght 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 DC9473060AA8; Thu, 23 Jan 2020 10:58:59 -0500 (EST) From: Thomas Monjalon To: jplsek@iol.unh.edu Cc: ci@dpdk.org Date: Thu, 23 Jan 2020 16:58:58 +0100 Message-ID: <1827408.xz2uEaWSZ7@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [dpdk-ci] Intel performance test is failing 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" Hi, The test iol-intel-Performance is failing on all patches for a couple of days. It seems to be due to a perf drop with a 10G device Can we disable this test until we understand what happens? We need also to understand how to avoid such failure, and how to monitor and disable it faster. Thanks