From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] scripts/ci_build.sh: Don't fail on bullseye build errors
Date: Tue, 18 Aug 2020 13:23:06 +0200 [thread overview]
Message-ID: <20200818132306.35709675@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20200730160855.GB16281@yssyq.m.ilbers.de>
On Thu, 30 Jul 2020 18:08:55 +0200
Baurzhan Ismagulov <ibr@radix50.net> 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.
>
prev parent reply other threads:[~2020-08-18 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 20:08 Baurzhan Ismagulov
2020-06-22 7:39 ` Jan Kiszka
2020-07-30 16:09 ` Baurzhan Ismagulov
2020-08-11 7:01 ` Jan Kiszka
2020-06-22 10:42 ` Henning Schild
2020-07-30 16:08 ` Baurzhan Ismagulov
2020-08-18 11:23 ` Henning Schild [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200818132306.35709675@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox