From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6840895692641140736 X-Received: by 2002:a17:907:b0b:: with SMTP id h11mr3442623ejl.371.1596125339395; Thu, 30 Jul 2020 09:08:59 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6402:1d37:: with SMTP id dh23ls5994280edb.1.gmail; Thu, 30 Jul 2020 09:08:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJySPKOEwj0W3Se7tVGwfGoMwneyJ2UXA02fbF6P78sSvBv53BIYkXrtY9ZzuNHjAf4J/fkS X-Received: by 2002:aa7:dbd9:: with SMTP id v25mr3482107edt.137.1596125338823; Thu, 30 Jul 2020 09:08:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596125338; cv=none; d=google.com; s=arc-20160816; b=JN3mWVGvJ4BPmE0nHTsxyBzFr9LPBMtt8hvU6zoT6ZQiADp3q8CFtPEuxvMcneucIX ICpHR7Ti37h32o9UOWM+iBTmVAEMJ/sduT64mCNKxGBP4IX3EicZq8tQzq0G5vMmly9/ OXeyUEco2zhBlUFbfu8vKK9u5xp7mBZ4keRisU3xkEYdJEY/lc8TyCYOaXGDC8f2ldlE paNcWXYnefp0WrndNX7khm4PK/R1Wi/O3c/6ZiY7IXR8+PPKo89kcVYOuVtTMAzlZLLq Bxk4hurX3YjcYwWgptn2JgPhu/+aLDMOQnCp1tQcY918YvE8ngjm83FqzpuV2BQdbrjn pXnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=y3eJNI2wTNh3l8K/bqWimWHGD4zIOcNXH8upT9EE1Hc=; b=JGV07lhzAvfjFeySiVmy7W/OovLzVI5ASolMo++ym6hi70ZLtaJicniTH8sqGnBLDD /z8mMIYx8dn0W/wwY6Hl84mcwmiMupm830oQvw+M4QiG6Jnd/VZAhBdrO0KupUPFYlQ6 7nbmSfcY8K720kmcHdPMC5W7/thDvtkIqwA305bgrRR+HThziRDaZDOOMKPggDc/ZVla kLOij8Z8CqL5OIm+GwYefk+st4/DNoTZ0zE3Z4wgwrv4UGNaIO3kXNL7yEgOjFE/XYyI dYe3WUzW0mzQCNFE3wKUb/gw4Vi2hxV1epZ5jIvWHmNZmqZK3akdYOeUJsXfbZKNA2lx 8XMQ== 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 o23si318403edq.5.2020.07.30.09.08.58 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Thu, 30 Jul 2020 09:08:58 -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 yssyq.m.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 06UG8tQf001517 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 30 Jul 2020 18:08:58 +0200 Date: Thu, 30 Jul 2020 18:08:55 +0200 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: [PATCH] scripts/ci_build.sh: Don't fail on bullseye build errors Message-ID: <20200730160855.GB16281@yssyq.m.ilbers.de> Mail-Followup-To: isar-users@googlegroups.com References: <20200621200843.23865-1-ibr@radix50.net> <20200622124251.2db7d6fa@md1za8fc.ad001.siemens.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200622124251.2db7d6fa@md1za8fc.ad001.siemens.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED 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: XOsBm+zyByZ3 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. 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.