From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v12] devtools: alert on new instances of rte_panic and rte_exit Date: Thu, 26 Jul 2018 23:00:26 +0200 Message-ID: <2274773.jc5eBGUB0q@xps> References: <1531741077-5513-1-git-send-email-arnon@qwilt.com> <5378502.1ef9rKBE6e@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, "Burakov, Anatoly" , "Lu, Wenzhuo" , "Doherty, Declan" , jerin.jacob@caviumnetworks.com, Bruce Richardson , "Yigit, Ferruh" To: Arnon Warshavsky Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id E0D1A288C for ; Thu, 26 Jul 2018 23:00:32 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 26/07/2018 22:57, Arnon Warshavsky: > > > + if [ $? -ne 0 ] ; then > > > + ret=1 > > > + fi > > > + printf '%s\n' "$report" > > > > You are printing the report, no matter of the result? Why? > > Is it because a warning does not return as an error? > > > There is maybe an improvement required here. > > > > Yes this is indeed the reason. > Sticking to a simple success/fail in the return value with the price of > printing an empty string in the case of no-warning seemed better than > handling multiple (>2) return codes . > Do you have a preferred way here? My preference is to return an error if there is a warning. The script itself must return an error code. Thank you