From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 23B431B341; Fri, 19 Jan 2018 16:45:02 +0100 (CET) Received: from cpe-2606-a000-111b-4011-eaa3-4b92-4a68-8f24.dyn6.twc.com ([2606:a000:111b:4011:eaa3:4b92:4a68:8f24] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1ecYqe-0002Ao-HC; Fri, 19 Jan 2018 10:44:58 -0500 Date: Fri, 19 Jan 2018 10:44:24 -0500 From: Neil Horman To: Thomas Monjalon Cc: dev@dpdk.org, Bruce Richardson , john.mcnamara@intel.com, qian.q.xu@intel.com, ci@dpdk.org Message-ID: <20180119154424.GC9519@hmswarspite.think-freely.org> References: <20171201185628.16261-1-nhorman@tuxdriver.com> <20180105160052.GB18004@hmswarspite.think-freely.org> <20180109013210.GA26043@neilslaptop.think-freely.org> <4728124.4p1ub5D4TT@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4728124.4p1ub5D4TT@xps> User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Score: -2.9 (--) X-Spam-Status: No Subject: Re: [dpdk-ci] [dpdk-dev] [PATCHv3 0/4] dpdk: enhance EXPERIMENTAL api tagging 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: , X-List-Received-Date: Fri, 19 Jan 2018 15:45:03 -0000 On Tue, Jan 09, 2018 at 10:20:05AM +0100, Thomas Monjalon wrote: > 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. > Ping, I thought you were going to integrate this? Its been sitting here for over a month now. Neil