From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 9D894A0096 for ; Wed, 5 Jun 2019 14:25:23 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6D6481B9FD; Wed, 5 Jun 2019 14:25:23 +0200 (CEST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by dpdk.org (Postfix) with ESMTP id A29E51B9DF for ; Wed, 5 Jun 2019 14:25:21 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 2F950256; Wed, 5 Jun 2019 08:25:20 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 05 Jun 2019 08:25:20 -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=sfOoS6sgnfFDEjgFek3vYrS/iUUmcT8O1k0Eqy1vPVI=; b=lAez2A/ZHvFK YyGwgfvi2zJSpXIU10ImQ6RZ7NUsOfqsggL0Z/F40QnwtRKLHBL8Az5jsTNnnIVF 0R5MsDyzLzR3O26CKKJg4RXEQoOT825Qkat8VRQmzbEfZQxXceiMTrPhMSeso3Z8 jg8mUp9za/G1HvtgJQatQXiiSXvGxeM= 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=fm2; bh=sfOoS6sgnfFDEjgFek3vYrS/iUUmcT8O1k0Eqy1vP VI=; b=2RO6dVI1jzXS4Bi7O2hGtlYm9ncH0zSGOt0XuVhKxQmkcQkCgHmDToi3K 7fGlMqpyZBoNfeYyCn2wCQR/CnTl32pzNobzZP2odnMpBvikDAvhXzUOWh37gAH2 EuIA5zQPDqcXtvLtNNyS5nubHX8ZFTgFPfsre21S6+noi8ZeQVkiQfqO6VY95NAq YLJVYlatstw+uxH/s53FduBsl5trmd6bWugKblkvbJSFpEkCNT9DcdqeD3ifdTpA pR1U/iHjv5t/DsCSrT0Worjarq72WCqoNew8COJLlJsl7cAEDT07nrIh/q09gTad bs7iaJF0osRyJO+6AXwllWWCrkY4Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudegvddghedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen 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 0132480060; Wed, 5 Jun 2019 08:25:17 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: David Marchand , Declan Doherty , pablo.de.lara.guarch@intel.com, qian.q.xu@intel.com, zhaoyan.chen@intel.com, xuemingx.zhang@intel.com, john.mcnamara@intel.com Date: Wed, 05 Jun 2019 14:25:16 +0200 Message-ID: <10915192.JeauKhfVku@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] aesni mb on Centos KO for three weeks X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" +Cc more people 05/06/2019 14:05, David Marchand: > I noticed build errors on patches I sent yesterday: > http://mails.dpdk.org/archives/test-report/2019-June/084633.html I tried to reproduce this error with make on my system but I don't manage to see such error. It may be specific to a GCC version. > I went and looked at the test-report mailing list. > > The failures on master builds started on May 14th: > http://mails.dpdk.org/archives/test-report/2019-May/082432.html > But still, the test was reported as successfull. > > The status got properly reported starting May 28th: > http://mails.dpdk.org/archives/test-report/2019-May/083421.html > Looking at patchwork this day, I can see that it changed between > http://patchwork.dpdk.org/patch/53721/ and > http://patchwork.dpdk.org/patch/53722/ > > So I suppose someone noticed that the meson build failures were not > properly reported and fixed it, but the error still remained. > > So, we have this error for 3 weeks, is there someone looking at fixing it > please? > I did not manage to build the ipsec_mb thing on my rhel. > Not sure what is wrong, but I don't want to waste more time on it. > > > As a sidenote, we don't have Intel build reports on the patches since this > morning, around > http://mails.dpdk.org/archives/test-report/2019-June/084647.html > Has it been disabled intentionnally? I agree with David that there is a serious issue with compilation testing for a long time. Please can we fix it quickly?