From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7097264153945964544 X-Received: by 2002:a17:90a:6284:b0:1df:4595:57af with SMTP id d4-20020a17090a628400b001df459557afmr4806462pjj.188.1653402223836; Tue, 24 May 2022 07:23:43 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6a00:2352:b0:518:5159:a6e4 with SMTP id j18-20020a056a00235200b005185159a6e4ls6193221pfj.9.gmail; Tue, 24 May 2022 07:23:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxtHIYPtudWWx6yCoEAvSTgDprpq0urCAcjf1pVoRhVfzw7PV3tLquQ3l4/VpPFpXwo5rMg X-Received: by 2002:a63:8449:0:b0:3fa:aa30:cae0 with SMTP id k70-20020a638449000000b003faaa30cae0mr2988115pgd.498.1653402222819; Tue, 24 May 2022 07:23:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1653402222; cv=none; d=google.com; s=arc-20160816; b=gaKVRhSFJLa6YxFC3RnKLThHJWFOLY5mPaovwJEqH0f1hM980eQpUAzufn117Max/x +XVlUuOSXRYPGnl+pbqSNt+DWaPb/v0YjkBFKLBCjd/RqDSeuNOZjFA4t4GxfOE8OzJU 5D2WiF1Zkztdewkop6J2DE/6dU6hPuQrVAbufVK5tLPS50nxReQ8hLVWPPGn3LgfXcG5 TQwbekj2aHFVWmkJr6PuiUu7p5P1j1M5r+18MdygaN+yIYDjeR19DLk4H4Y79VKIrHKW 1PrnbG0ibISpijywPUCFdqUgySbxoP1zJAEc5p2EZS18GkcEmFHXBu5V5XBGnewGRTc+ y0tw== 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:cc:references:to :content-language:subject:user-agent:mime-version:date:message-id; bh=wz6bwmVIJSB4701vCKYOANNBODE05wUL4nUOj/UvctQ=; b=fBW8CBMGNJ8UbJ4kpeauBgpcZVj8nAOvyVJf0rqON2v+MXyBis1mM/AC2Qa2LWdf7T bvcfHl8sqYHIRM6sUVJluCvZp4bWxW5RxQAfvZip6buGLHo/N+tXFUbjc9tdqy24kRtB OV7YnQ3r0drxsHGUTjOmtqgP2i/rAjFMAFI2urgeMA+YO7tSt7d7IGC1zfGZazYZvGj8 CQoJLvKQXhGOi0Hme0O60uXVjjfNYTpEHF8ipaGByHYO10apLqFM/CfIt0Pqx2wLmeNu 2meJuuq8wRqnANbf7hBCa8fYnxygsrGXx52W4WksfS+OG6vpw1I9LfUydUbgB4kZdCKf F5+w== 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 lr15-20020a17090b4b8f00b001df25a64c1asi119670pjb.2.2022.05.24.07.23.42 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 24 May 2022 07:23: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 24OENcPL029786 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 24 May 2022 16:23:39 +0200 Message-ID: <5bb4f88d-0285-4407-6bad-04e6b6e3703f@ilbers.de> Date: Tue, 24 May 2022 17:23:38 +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 References: <75340600-5180-2f78-86f8-d5dc0c757a35@siemens.com> <3ddcda7f-41ba-5e25-3ec8-959a5ff356cc@ilbers.de> <46894ccf-242c-68fa-1553-b99a5670c160@siemens.com> Cc: Baurzhan Ismagulov 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: x2jjDRckjGTd 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 > I didn't find any differences between Yocto and Isar. If putting glibc_2.35.bb change example into Isar it behaves in the same way outputting full error log. Otherwise if executing the second example in Yocto (running bash code from python task with bb.build.exec_func) it will output only exception message just like Isar. So there are no issues in Isar itself, it behaves just like Yocto. If we need to have full log printed Bitbake should be fixed.