From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7097264153945964544 X-Received: by 2002:a1f:32cd:0:b0:357:5ee6:d6b9 with SMTP id y196-20020a1f32cd000000b003575ee6d6b9mr5684668vky.32.1653378223297; Tue, 24 May 2022 00:43:43 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a67:df9a:0:b0:32c:27bd:37dd with SMTP id x26-20020a67df9a000000b0032c27bd37ddls2848998vsk.10.gmail; Tue, 24 May 2022 00:43:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyuPfoOraJ/c0hDa9Gp+0cA/rWjq9SqImgRgs4ABsTIXmEH9Mj/ODP7gBtyg/VypmWHvppN X-Received: by 2002:a05:6102:1624:b0:337:6e66:12a2 with SMTP id cu36-20020a056102162400b003376e6612a2mr7761293vsb.62.1653378222678; Tue, 24 May 2022 00:43:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1653378222; cv=none; d=google.com; s=arc-20160816; b=f4Uc+YY+a2KEmOQ2dsvcaUlKuhKuEtZxSKohga6gk5tpjofuAdbvEo9GlfDCF5OMYk JN17F8orK8dWcc0sIuEJ8SfL8scgTD/heia/o5Z6HLUdYhUnnrgmYGfeTKLb6ebG32qk JcpcgxxsHmMCnyQbWLMFY7yV9G3s+8vapf4qgeLiM+K6qG60S6gt6OnMH2+w20YhI0HO gQP/5GVVwpxOs1EKStA0DxjQM1Zlv98KcOGdbCzJvlGmJPV8F2yp+2MoUrhgarUXKXs2 I1F+Gqp8/mAOCCZk580xoeJL68pk7OwNzReed8igIxkOBZtchKxgP6UIOb9RHhpV0CdR 5YTQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id; bh=hjdgdOSQHUdpy648jvSvKB2bHJ6kxRaO7ossHLNSicA=; b=RoKhQOf2YLYzdc/rLmd1H3d1YDO4v3sWYIMqAsu8Su8is6jajFcH/QzIAScE9P+jt2 gsr7o38y8unaJC2FqJAXWuLXrzleqg+YuTF/MkA0yo5vkV7Mr4LpwC2goYWj8rNSQ4XW DkBy109lDIaCSWwe8GWQko3/Jtp2oR/+fCREw7bxteTVG1Y1hRKjPEeYkr0+RxzHS8wu vCUY25KJ8LLTMNR8FNF9kxOcYojWmIviKggkvr5zCLYd34LRDyfOC6cvUC0Ds8qsODlb Sp1FS5AhGXpp7QEOhy9Cj0FAggymyqVysgvPos0tYr9XjhPZ9oWXII+kegnOYdVxwUPO 54XQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=amikan@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id bj27-20020a0561220e5b00b003574e1867f6si742924vkb.4.2022.05.24.00.43.42 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 24 May 2022 00:43:42 -0700 (PDT) Received-SPF: pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=amikan@ilbers.de Received: from [127.0.0.1] (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id 24O7hcsc028562 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 24 May 2022 09:43:39 +0200 Message-ID: <3b3b3f82-ad94-1853-a58f-f3fa878549e9@ilbers.de> Date: Tue, 24 May 2022 10:43:37 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Error logging broken with next? Content-Language: en-US To: Jan Kiszka , isar-users , Baurzhan Ismagulov References: <75340600-5180-2f78-86f8-d5dc0c757a35@siemens.com> <3ddcda7f-41ba-5e25-3ec8-959a5ff356cc@ilbers.de> <46894ccf-242c-68fa-1553-b99a5670c160@siemens.com> From: Anton Mikanovich In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: fLZAyiKG0ki5 23.05.2022 22:06, Jan Kiszka wrote: > It's actually much simpler: Just call "bitbake borken-target" on the > shell, and you will only get the lengthy backtrace but not log report. > > I'm not yet down to the core of the problem, but when you force such a > failure in upstream poky (today's master), you also get no immediate > output of bitbake - but then the knotty UI jumps in and does a > > Log data follows: > | DEBUG: Executing python function extend_recipe_sysroot > ... > | DEBUG: Python function patch_do_patch finished > | DEBUG: Executing shell function do_fix_readlib_c > | FAIL! > | WARNING: exit code 1 from a shell command. > | DEBUG: Python function do_patch finished > ERROR: Task (/poky/meta/recipes-core/glibc/glibc_2.35.bb:do_patch) failed with exit code '1' > > > I've done this to poky to trigger it: > > diff --git a/meta/recipes-core/glibc/glibc_2.35.bb b/meta/recipes-core/glibc/glibc_2.35.bb > index 6ea5b1efb5..9500c8a128 100644 > --- a/meta/recipes-core/glibc/glibc_2.35.bb > +++ b/meta/recipes-core/glibc/glibc_2.35.bb > @@ -91,6 +91,8 @@ do_patch:append() { > } > > do_fix_readlib_c () { > + echo "FAIL!" > + false > sed -i -e 's#OECORE_KNOWN_INTERPRETER_NAMES#${EGLIBC_KNOWN_INTERPRETER_NAMES}#' ${S}/elf/readlib.c > } > > Analogous trigger for isar: > > diff --git a/meta-isar/recipes-app/example-raw/files/rules b/meta-isar/recipes-app/example-raw/files/rules > index a1167375..ed63d364 100644 > --- a/meta-isar/recipes-app/example-raw/files/rules > +++ b/meta-isar/recipes-app/example-raw/files/rules > @@ -5,4 +5,5 @@ > # we do violate debian quality rules here, but on purpose to demo how > # to deal with it > override_dh_usrlocal: > - true > + echo "FAIL!" > + false > > So, Isar has a bug here of not letting knotty (as default UI) do its > job it seems to me. Didn't this work before? Didn't we also have those > duplicate dumps in the past that upstream bitbake seem to have resolved > now? > > > BTW, I've received first reports of this bug from the field today. We > must fix this before the release, or our users will kill us. > > Jan > Hello Jan, Thanks for example. The question is how the same bitbake version can work it different ways for Yocto and Isar. I will try to dig in and let you know if found something.