From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6526857818487652352 X-Received: by 10.80.232.139 with SMTP id f11mr1887094edn.5.1519995868821; Fri, 02 Mar 2018 05:04:28 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.158.236 with SMTP id a99ls4909961edf.7.gmail; Fri, 02 Mar 2018 05:04:28 -0800 (PST) X-Google-Smtp-Source: AG47ELutHpN81gew4ipNkFRRjJ3y/v38LYNH0f6+w5X3rtQM4xz0NMtk2S7kiQNdytqm5E0wAsaL X-Received: by 10.80.232.139 with SMTP id f11mr1887087edn.5.1519995868226; Fri, 02 Mar 2018 05:04:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519995868; cv=none; d=google.com; s=arc-20160816; b=tBjBBEgvLUhEFMR5pHotasqUGuvgtwFqAzz8Dq/1rroNP+XiP48L4J8DTz3WuPSMuH TfWDTYEsEEl2SdLFqp4jSiPj75cs7oqs8p9C/ccyBJ5JoARq1CxgGPSCPP5fZABSJ+1h vesZLhKhZV4goSZ0YdF/4ngTQNP/wAo7GiUmJLYvd9Yhu/TasZwhETe4sHTjuCOf0vHA wQ+oCHTNuJdnC5nt2hONk5V8uwTm//DNDa9a0hSU7MCZx1O/4SYeaxMSmMSvUORYgEwg 0me9+a3e9O3tc4v2ZESM+EnN+3E/xhXgjgk8qPuy7f8tswa4TyFcWIHeSIJC5x6wKhjf V+Fw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :arc-authentication-results; bh=bqtjlffWnqyAU1F/rihEG5qgjCTn5cK76xlk0F3BdA8=; b=w+hVJDg8lFwhtagLf1e0o+vQ8Yrjr3pUOJCBqFSCggVhZ+ynps0HoCE1qcQTy7MPQw 6EgddxqdWVDwMy/C/v/TzifQ5H8/KYYF8Q7gcnLz+sX32A3maC63/d8zP1PHIJdrVB4M 5abpZ+ikAONJanMomrjFaynKPeCii3R3qelhoXfZSwUv4C21F+L7q+52wcWmgwJri4iM lZtyspZ3nXVFuoWxr8Ju7qBNuV3MdzNPO5pf36i1g6FxdcFXxvHeAUZbjjMmMvWWB6Wq 0xFtcxkG2gKQCbvqSIbkqYPZW6XLPBVhUB5jufuSCoN3rwaM7MOiJsNQnrNvmecs+4Ln +Ksw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id h9si299168edi.4.2018.03.02.05.04.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Mar 2018 05:04:28 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Received: from [10.0.2.15] ([188.227.110.165]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w22D4PYs029063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 2 Mar 2018 14:04:27 +0100 Subject: Re: [PATCH] Include error log of failing task in output To: Jan Kiszka , isar-users References: <955aab45-bca0-7458-e3d6-a90616d2cbd7@ilbers.de> <34f64f37-d5ec-5135-96aa-5e1a99d6c264@siemens.com> From: Alexander Smirnov Message-ID: <5c9f3414-e119-53be-5283-9278a8637bb4@ilbers.de> Date: Fri, 2 Mar 2018 16:04:20 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <34f64f37-d5ec-5135-96aa-5e1a99d6c264@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: u8s4HP91PKz9 On 03/02/2018 03:46 PM, Jan Kiszka wrote: > On 2018-03-02 13:43, Alexander Smirnov wrote: >> >> >> On 02/26/2018 04:41 PM, Jan Kiszka wrote: >>> From: Jan Kiszka >>> >>> Particularly helpful in CI environment, but it also saves many manual >>> log dumps. >>> >>> Signed-off-by: Jan Kiszka >>> --- >>>   meta/conf/isar-bitbake.conf | 2 ++ >>>   1 file changed, 2 insertions(+) >>> >>> diff --git a/meta/conf/isar-bitbake.conf b/meta/conf/isar-bitbake.conf >>> index b49386c..8a1d86b 100644 >>> --- a/meta/conf/isar-bitbake.conf >>> +++ b/meta/conf/isar-bitbake.conf >>> @@ -42,6 +42,8 @@ BB_STAMP_POLICY ?= "full" >>>     BB_NUMBER_THREADS ?= "${@bb.utils.cpu_count()}" >>>   +BBINCLUDELOGS ??= "yes" >>> + >> >> Is there any specific reason of using the weakest assignment here? The > > Because all tuneable confs are included after this statement. In my understanding, tuneable confs should not contain "?" marks in assignment, because they specify concrete configuration. :-) That's what I see, for example, in local.conf file. > >> whole file contains "?=" only, for me this looks enough here too. > > That's likely a bug to be fixed separated. What is your overall policy for assignment in this case? Alex