From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id E30831B16B; Tue, 9 Jan 2018 10:20:30 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 60C3D20AF0; Tue, 9 Jan 2018 04:20:30 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 09 Jan 2018 04:20:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=RcXVZIIhEhuy5ejMbK8VQ13/q/ dvhOsnCz/NxconMvU=; b=PJFSMTzE67h/oMPLxF06wjhmqzUqPXcwBNN8n2Z5oJ fG6czFPE63+fyz28K4TkeVBk3+AS604aimbwcTZiwbBwQINemtsR1UJEf9tVYTm7 CdgHHaZ6ZH7HXee73L34qvP90dPF9dHceniEbwkpiRUngphb8m/ntsQ943ndwa8B g= 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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=RcXVZI IhEhuy5ejMbK8VQ13/q/dvhOsnCz/NxconMvU=; b=qL7yhUu22NUrpc9dgIMo6Q UxsX8xCps7vNqkAhXRIZVkh/PAH0lv9JpL7F9QeW1doVbrNsa3CAvZhoKndAC9nr gkD+1mphXMjjS3BiXT5caT+vJpoHKKpWzKUsPuKfGa5KK2H6yW7SZH6T16FhaVmO BJaiFwaRun+BEcp48QntTOGGaYe2tY08EX+15ER+O+pT5/hrn/hD9Jl2EB0CCGFz 88n5cZD8WVC7twpVMWz8O86v+DljgMqBQYug7r5AOdWBnRSxW+dzLGBC4SnEDPel BTbQSQWatfV27IS4e589pqVtWErS57haNOe8pElPviVWqvxadPSxPq/tTb9OdBGg == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 02D2A24736; Tue, 9 Jan 2018 04:20:30 -0500 (EST) From: Thomas Monjalon To: Neil Horman Cc: dev@dpdk.org, Bruce Richardson , john.mcnamara@intel.com, qian.q.xu@intel.com, ci@dpdk.org Date: Tue, 09 Jan 2018 10:20:05 +0100 Message-ID: <4728124.4p1ub5D4TT@xps> In-Reply-To: <20180109013210.GA26043@neilslaptop.think-freely.org> References: <20171201185628.16261-1-nhorman@tuxdriver.com> <20180105160052.GB18004@hmswarspite.think-freely.org> <20180109013210.GA26043@neilslaptop.think-freely.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-ci] [PATCHv3 0/4] dpdk: enhance EXPERIMENTAL api tagging 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: , X-List-Received-Date: Tue, 09 Jan 2018 09:20:31 -0000 09/01/2018 02:32, Neil Horman: > On Fri, Jan 05, 2018 at 11:00:52AM -0500, Neil Horman wrote: > > On Fri, Jan 05, 2018 at 03:08:52PM +0100, Thomas Monjalon wrote: > > > 04/01/2018 13:56, Neil Horman: > > > > On Sat, Dec 30, 2017 at 12:15:17PM -0500, Neil Horman wrote: > > > > > Thomas- > > > > > I just noticed that the ci tests are failing on the intel compiler, which > > > > > makes very little sense to me, as the error is a permission error on a bash > > > > > script that added in this series, which works during the gcc compilation. Can > > > > > you take a look at that please? > > > > > > > > > > thanks > > > > > Neil > > > > > > > > > Ping again Thomas, I've still heard nothing from you or the CI group about > > > > getting more visibility into the odd permission problem in the CI runs this > > > > seems to be encountering. I'd love to fix it, but the information in the report > > > > is insufficient to have any idea whats going on and the problem does not occur > > > > on local builds. Please advise. > > > > > > Unfortunately, I have no clues about this setup. > > > The report is sent by sys_stv@intel.com. > > > Adding Qian as Cc. > > > > > > The error is "buildtools/experimentalsyms.sh: Permission denied" > > > And the file mode is 100755. > > > > > > Anyone from Intel to check what happens please? > > > > > Thank you Thomas. I would really like to get this pushed in, as others have > > acked it, but the lack of visibility into the CI errors is quite frustrating > > Neil > > > > > So I'm not sure where to go with this. I've emailed the ci group on their list, > I've asked them directly on this list, and asked you, Thomas for assistance in > getting hold of the ci maintainers, and there has been no response in over a > week now. This patch has been acked by a few people, and the builds work on > clang and gcc locally just fine. I'm inclined to ask you to take these patches > despite the ci errors. If the CI maintainers can't respond to needs for > visibility into the system, I don't think its reasonable to block patches based > on CI results. > > Thoughts? > Neil Yes, you're right, we can bypass this CI test.