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 DD939A00BE; Mon, 27 Apr 2020 17:00:31 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B18A91D56E; Mon, 27 Apr 2020 17:00:31 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 7E6B61D56D for ; Mon, 27 Apr 2020 17:00:30 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id EA6435C01E5; Mon, 27 Apr 2020 11:00:29 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 27 Apr 2020 11:00:29 -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=fm1; bh= 3VAY/jV1MKLVNQh13MlbYPDHBTWctCrauJHR/RdW+o0=; b=XlzrP1V+B9DfkCpz uQUbQJXxu5hPhnD2U5B3xznPH36j+vBUKVnlA9bKW7bpTFTImb207AaB0ZT8stTC +Md6wos/whne0qLKBPRCMNJsZMElzxrNOVTdLilQiEgu20cWHWWuBJAF6py65IS2 jjqias9ijTCle5Or9bVz70Ck6pRtQNbUPKDSZd7OMg+F5iXa+b+Yw1KqLEWS5E9m k6SeKT6urb7SMNkWlA76TweeYmld0A1LilMjUM8rzhs2KQf69QSmncuCzVByAiIP 6gT+kUJd6O7rb9L5VHkduA6NkalQQ0Wes4q19Db8CC+bdeS+f/CMnQa56IjBQmag nEGHXg== 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=3VAY/jV1MKLVNQh13MlbYPDHBTWctCrauJHR/RdW+ o0=; b=jMYyork9WO2yJ/0/xEqOtxEFvlq/5W8b59mCQQ5C9el8Hbbz7eEcUZw7Q IxVY/Tgdyl5ehGOAhorHwkvU3+Z3lbN/dfjMJOYxGSk/rJqRjJl+B5RQhlHzSCvL 1OvgwiMJFBi5fdXBM3iiBwNP5/XVAyj+PMmOJukBZ0+3hHVQ01Y6juRdtF/DeuSw zVVMpz2zoD53wR/WyGdpRLvfczqX+R8QMRqLGqmQ8G/AhnCgrDhSJ1rZtcsXVl+Y KSmrszH9D/VlO0BYFrpIbE3biY67KtcOr1XQjq9gTpaAcMuKAFcztMagWP1EYlJk G/jHetH0e2D/wSrw0meT9FQdaeUkw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrheelgdekudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth 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 6A8233280069; Mon, 27 Apr 2020 11:00:28 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit , Aaron Conole , David Marchand Cc: "Somalapuram, Amaranath" , "Kumar, Ravi1" , "dev@dpdk.org" , Raslan Darawsheh , Ali Alnubani , dpdklab@iol.unh.edu Date: Mon, 27 Apr 2020 17:00:26 +0200 Message-ID: <529334320.JY4mfKhWER@thomas> In-Reply-To: References: <20200427061145.25039-1-asomalap@amd.com> <22a7429d-067a-4dc1-ca86-c45a776b4d69@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1] maintainers: update for AMD xgbe and ccp crypto 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" 27/04/2020 14:58, Aaron Conole: > Ferruh Yigit writes: > > [1] Two issues reported > > a) ninja: build stopped: Error writing to build log: Disk quota > > exceeded. > > This occurs on some of the ARM64 builds. Travis is aware of the issue, > but don't seem urgently fixing it. :-/ I think we have a series > outstanding that should be applied to drop those builds for now. I saw some "Disk quota exceeded" on x86 static builds. So I changed my mind, I am not sure dropping only Arm from Travis is a solution, even temporary. > > b) No output has been received in the last 10m0s, this potentially indicates a > > stalled build or something wrong with the build itself. > > This is a future enhancement I need to work on. When a build has jobs > that are stalled / errored, we need to restart them (at least once). Or > otherwise flag it. It especially happens when internal travis > infrastructure fails. Yes Travis infrastructure fails. Always. Travis is free, but it is not a reason to provide a randomly failing tool. I suggest switching to other platforms like OBS or our community lab, preferring the most reliable one.