From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7101979564966936576 X-Received: by 2002:a9d:2c1:0:b0:60a:fac7:48d1 with SMTP id 59-20020a9d02c1000000b0060afac748d1mr12567081otl.84.1653638869306; Fri, 27 May 2022 01:07:49 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6830:2a10:b0:605:54d2:50da with SMTP id y16-20020a0568302a1000b0060554d250dals5299573otu.8.gmail; Fri, 27 May 2022 01:07:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxgsYIiFwCV6pecLcC11Pnty0M54PWnuSncIKdSvbraVFKIyBCdMWSsnqFAlDQfPTaP8BXK X-Received: by 2002:a9d:6e97:0:b0:60b:3a60:142b with SMTP id a23-20020a9d6e97000000b0060b3a60142bmr3587166otr.217.1653638868719; Fri, 27 May 2022 01:07:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1653638868; cv=none; d=google.com; s=arc-20160816; b=G2Y5Jlojz6NsM3jAbyuK05Nlfp+E0c94pHWg6wuKMbretZJfetdQGIXSnOdiZwdrFa +FU5/GPVwqbl+NoDA3+59Xmoq6byUfFvksXhu0O6iQdMO68vHm9N5duqNhOMDRkmsXn3 Fj+zSYymM8CHH52E7G0yq11hTJSu6oB9crEAgjCCJE+2R8HtPpsiLqcnGpquJPzYCtLG 7JTK8GEKhdbTqI4p1i+iKN4YMN4M8u26jDNB7u2G9/MSookczIl2KfFaY25h0AMSVlYs sVXCcsd1AiCugLrsI919NVk0Cj7lp3wpJnKC4kfANcT3fnP0Iz0DwWVzJJEMyw3pzKMo duMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=s/1KkMlphSbTcve4PbqOVzWl6MMLLoNzTDMq3b7x7I8=; b=WSKe1DxWmNZpwzOc/pP4L0jgV48IfoXxh5MNeZMHKb2mor+CIUO+65df83oDmaXdaV jipOQkKJGG8kk0/lIAI1HEiFtZTg6TnUR4wGd4HUG73DGK18tXFcNrogLbPYiI1UHJ5u QuzXx2pCImiHbos0s72PEOz1G4wz/I1D6gPfEcHMSRT+GnSieRwLjEEHDblRHSKKmdQE Grw7V0k21bW1qu+59MMGyVEyRo1izPe57OMD1PnY3kd+mzo4VqZX+Ja7sJm4L4OUMSQ3 N4JllsJwqxVcTEK2paRSOescihfKaeu3+JA074Icp4//LFt4cZtuWYFs9Urs0TkXi95p 59NQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id gh24-20020a0568703b1800b000ddac42441esi255970oab.0.2022.05.27.01.07.48 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Fri, 27 May 2022 01:07:48 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from ilbers.de (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 24R87j79011059 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 27 May 2022 10:07:46 +0200 Date: Fri, 27 May 2022 10:07:45 +0200 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: [PATCH] utils: Ensure shell function failure in python logging is correct Message-ID: Mail-Followup-To: isar-users@googlegroups.com References: <20220526094739.6340-1-amikan@ilbers.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: K3Sl+Att347s On Fri, May 27, 2022 at 09:53:24AM +0200, Florian Bezdeka wrote: > On 26.05.22 11:47, Anton Mikanovich wrote: > > If a python function exec_func() calls a shell task, the logging wasn't working > > correctly in all cases since the exception was turned into a BBHandledException() > > and the logfile piece was lost which is handled at the top task level. > > > > The easiest way to avoid this is to allow the ExecutionError exceptions to > > be raised to a higher level, we don't need the traceback for them. > > Upstream first? Why can't we ask bitbake guys to do the backport and > lift our bitbake version afterwards? Is that already ongoing? We had checked https://wiki.yoctoproject.org/wiki/Releases: * 1.50 is EOL * 1.52 is untested with Isar and its support ends on Tue That is why I think the optimal next step is to migrate to bitbake 2.0 after the upcoming Isar release. This patch addresses the request to get the problem fixed ASAP before the release. If anyone volunteers to drive the upstream discussion -- I don't have anything against it, but I'd be reluctant to delay the Isar release if it takes longer. With kind regards, Baurzhan.