From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] Include error log of failing task in output
Date: Fri, 2 Mar 2018 16:04:20 +0300 [thread overview]
Message-ID: <5c9f3414-e119-53be-5283-9278a8637bb4@ilbers.de> (raw)
In-Reply-To: <34f64f37-d5ec-5135-96aa-5e1a99d6c264@siemens.com>
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 <jan.kiszka@siemens.com>
>>>
>>> Particularly helpful in CI environment, but it also saves many manual
>>> log dumps.
>>>
>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>> ---
>>> 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
next prev parent reply other threads:[~2018-03-02 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 13:41 Jan Kiszka
2018-03-02 12:43 ` Alexander Smirnov
2018-03-02 12:46 ` Jan Kiszka
2018-03-02 13:04 ` Alexander Smirnov [this message]
2018-03-02 13:24 ` Jan Kiszka
2018-03-02 13:57 ` Alexander Smirnov
2018-03-02 14:42 ` Jan Kiszka
2018-03-02 15:06 ` Alexander Smirnov
2018-03-02 16:31 ` Alexander Smirnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5c9f3414-e119-53be-5283-9278a8637bb4@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox