From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6840895692641140736 X-Received: by 2002:a17:907:724b:: with SMTP id ds11mr19515507ejc.481.1597749789132; Tue, 18 Aug 2020 04:23:09 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a17:906:e299:: with SMTP id gg25ls9495512ejb.11.gmail; Tue, 18 Aug 2020 04:23:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwl80W1SAGEDa3bXPRZkO7JgZ6Xu68hcIbJMsjkmvXjaAN+bR8gh5BHOI8bLrTdlZs/GsYs X-Received: by 2002:a17:906:aed4:: with SMTP id me20mr20512804ejb.141.1597749788365; Tue, 18 Aug 2020 04:23:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597749788; cv=none; d=google.com; s=arc-20160816; b=hqIeRgbG4UCzbx/ueXbi47/HGmUpm+nZJmSo/a43vO70Qnh7VPI8JrCBdF9ZQRFQbF ysa+W92IE0PdTdpZWnAPNmQR7AdWbOnfKmCanJuLp7FeyUVm03hZOM3VOgKKLkBfPruV wyiBpNy/RToMjtCM/6fTbmHRYP2tEmtnAl7seFePZs6MI1IlknZFJsteiAPFlVdVdTcb wN4/Okk5QAPSFptORONfI09kuQDSmTZJxYcyz2Zqb3GPhoBLDf/PEykU/ufj/V56qA9X Ef9wBiUSWbWJag/B0p2YEUus1R6CKYWSw+y/DmCfIyX1joJ4ThSjr05Yd6sFLYiXtdlG U6Rg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=Jb1P73VU3mm80Re3Uk3VKqmyvppI2AHPRO4KmYks1SU=; b=K1OIUCPgEzGD9+H00NAgpYB9VdgmeHjMFUiKY5lI9QNOKEMBsdloxqpV6ngl1/kaOu LZgdhZ3wogRMC9LzdPWzdc1l6emJPlJ8/+UbR1YzV3wGIJodBuyOrXHMKB2SNvH/0HP2 PGyjJDAapFFYzvJkkKUDHgZxFN+iNaugwo7stUHchcKdsfivfuj+UOee1YLrUC3jXr+I /0CIIQeOBK9cFiYq7lnwDi+21VZMk2JDyq1NWkiesAjSIFzM1PJc3SBAcaFuSlO6mPFA UGx419zPDsmamiZHANv1aN5AkX0xuI+Zjq8vYX/0rxtVOhSv3ycH61+Ge5FShlinW5we 07sQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id lw8si905345ejb.1.2020.08.18.04.23.08 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Aug 2020 04:23:08 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id 07IBN71M022710 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 18 Aug 2020 13:23:08 +0200 Received: from md1za8fc.ad001.siemens.net ([139.22.39.102]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 07IBN7lb030952; Tue, 18 Aug 2020 13:23:08 +0200 Date: Tue, 18 Aug 2020 13:23:06 +0200 From: Henning Schild To: Baurzhan Ismagulov Cc: isar-users@googlegroups.com Subject: Re: [PATCH] scripts/ci_build.sh: Don't fail on bullseye build errors Message-ID: <20200818132306.35709675@md1za8fc.ad001.siemens.net> In-Reply-To: <20200730160855.GB16281@yssyq.m.ilbers.de> References: <20200621200843.23865-1-ibr@radix50.net> <20200622124251.2db7d6fa@md1za8fc.ad001.siemens.net> <20200730160855.GB16281@yssyq.m.ilbers.de> X-Mailer: Claws Mail 3.17.6 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: WW+1SuJtJG1s On Thu, 30 Jul 2020 18:08:55 +0200 Baurzhan Ismagulov wrote: > On Mon, Jun 22, 2020 at 12:42:51PM +0200, Henning Schild wrote: > > We need a real fix for this. And if we go for a temporary skip we > > need a proper testing framework ... > > > > With this hack all we do is potentially introduce more problems for > > bullseye which will hit us when we have the fix, which we need > > anyways. > > I agree that bullseye must be fixed. The problem is upstream, so that > will take time. Did you report it upstream? Where is the bug? With you hiding the issue it is you who needs to do the upstream work. Henning > I also agree that we need a proper testing framework. It is actually > in place. As desired, every scenario has its own test case (a, b, c). > However, ci_build.sh tests many things in at once (a + b + c). Due to > that, the test cases don't result in the same coverage. Just adding > the two would double the time needed (a, b, c, a + b + c). So, I'd > like to find a good compromise. > > I agree that KFAIL may potentially hide further problems with > bullseye. However, as you mention in the other thread, it also blocks > CI -- that is, any work. That is why I think that unblocking CI has > priority over fixing bullseye. > > Applied to next. > > With kind regards, > Baurzhan. >