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 01A367D30 for ; Tue, 2 Jan 2018 13:39:53 +0100 (CET) Received: from cpe-2606-a000-111b-423c-e874-da8e-c543-d863.dyn6.twc.com ([2606:a000:111b:423c:e874:da8e:c543:d863] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1eWLr9-0006bX-4Q for ci@dpdk.org; Tue, 02 Jan 2018 07:39:52 -0500 Date: Tue, 2 Jan 2018 07:39:15 -0500 From: Neil Horman To: ci@dpdk.org Message-ID: <20180102123914.GB8096@hmswarspite.think-freely.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Score: -2.9 (--) X-Spam-Status: No Subject: [dpdk-ci] assistance understanding a CI report 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: Tue, 02 Jan 2018 12:39:54 -0000 Hey all- I was wondering if someone could help me untangle what on earth is going on with this ci report: http://dpdk.org/ml/archives/test-report/2017-December/036816.html The error is introduced with the patch associated with that build, and for the life of me I can't understand whats going on. experimentalsyms.sh is a script I added to the buildtools withthat patch, and it runs properly in the local git tree from which I comitted and sent it using gcc and clang for all the arches I have available to test with (power, x86 and x86_64). I don't understand why the ci environment would be having a hard time with permissions on the script, and don't seem to have any visibility into the ci environment to diagnose the problem. The patch in which the script is created: https://dpdk.org/dev/patchwork/patch/32234/ Correctly indicates that the mode of the file is 0755, which is correct. But as soon as I introduce its use in this patch: https://dpdk.org/dev/patchwork/patch/32237/ It all goes sideways. Any insight from the ci admins would be appreciated. Thanks Neil