From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7097264153945964544 X-Received: by 2002:a05:6000:1f91:b0:20c:54e5:fbbb with SMTP id bw17-20020a0560001f9100b0020c54e5fbbbmr13068353wrb.557.1652687389744; Mon, 16 May 2022 00:49:49 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6000:1688:b0:20c:67b9:e68b with SMTP id y8-20020a056000168800b0020c67b9e68bls16346951wrd.3.gmail; Mon, 16 May 2022 00:49:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzX+TruxKyNr5DPaWYnOkBWwWTUiSk5KT3o3MM7J4GVj9pWLr5dHiPMLzbVCyZvXH8r0nSn X-Received: by 2002:a5d:6843:0:b0:20a:def2:5545 with SMTP id o3-20020a5d6843000000b0020adef25545mr13065559wrw.89.1652687388769; Mon, 16 May 2022 00:49:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652687388; cv=none; d=google.com; s=arc-20160816; b=s2M4O71KN8VJGDteMR0QDwyvyLrI6h7xyqnEpZurFAUYBW2ThqB9FfDVIFfqDi87cs ATWwGnnE4XdldFD5Bz7c0iIFx5XUFEm6xYP8zNDOYNRBPhDh2LVgNTR4k3bsuIjjxKdf px91fJHox2qbEeL0sj18FW8qbUA1IyMUe7WQzx41N0TI1UPntUdayxns9b0K6DAz7QXD PoZ0Fy3UA5PO3/Ww2TZae6f8hAKuldG5v618bXIBBvbIYFENKAXRriPyAwMn8jyGAVAP 2CjfeF1m8O0rSENGPzW2STYbz2G7kRosRxTipybe1x+1IHXiEIlxqjfthoHFQyNf6a5m Y2Zg== 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:cc:to:from:date; bh=JabbdEky+/jcbQ25S1e3Jfcmc9TI2Op/1p1wbU4VOK4=; b=h/gaLFpDjT1k9SLKP2FsxHOr2plaLo4DDoStLLdis0UCnx1ItiPRddg42147Uw4B1B Ur7SJfIAjbfXj1RlJZBlrTGYH8ivd7TbQsDzp/3HuSMikqGMqpSuBB65592ikXBs+bhg N48qplubzwImaMSKur9cNln8sShOkbI3gBdntR99VIxRaDtk8KFbOBETmv27qS+upEg3 UazSpymbsOW0AxxvL9Y6vyCvVtB9bMtqlvCue/PuINWbClIQdfaGsQSjUtLzc6YdCBcS +HzFv64cI8yhQVDanu0o43ststRmPbfewO1aoOB5PrP48J7xllB5fVT9Pqruf3VvaKOi h37A== 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 m16-20020a05600c3b1000b0038e70fa4e56si689898wms.3.2022.05.16.00.49.48 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Mon, 16 May 2022 00:49: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 24G7nkBP001348 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 16 May 2022 09:49:47 +0200 Date: Mon, 16 May 2022 09:49:45 +0200 From: Baurzhan Ismagulov To: Jan Kiszka Cc: isar-users Subject: Re: Error logging broken with next? Message-ID: Mail-Followup-To: Jan Kiszka , isar-users References: <75340600-5180-2f78-86f8-d5dc0c757a35@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <75340600-5180-2f78-86f8-d5dc0c757a35@siemens.com> 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: JHy5iDPoYezc On Fri, May 13, 2022 at 06:49:37PM +0200, Jan Kiszka wrote: > I vaguely recall that you, Baurzhan, told me that logs of failing tasks > are not always dumped, right? I'm on current next now, building breaking > kernels, and all I get now is our useless python backtrace, always. All > is fine with log.do_dpkg_build, though. Is that the issue? Very annoying > and a no-go for CI. No time to bisect ATM, unfortunately. Can you provide some details for reproducing? Failure during make, or failure in the recipe? If you are running ci_build.sh -d, the complete bitbake output should be visible in stdout. If you are running ci_build.sh without -d, only a brief testcase list (1/23 repro pass) is shown for passing testcases. For failing testcases, stderr is dumped. One issue here is that bitbake captures stderr of its children and prints that to stdout, by design (https://lists.openembedded.org/g/bitbake-devel/message/13640). We are evaluating dumping bitbake stdout + stderr in this case. With kind regards, Baurzhan.