From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Schild, Henning" <henning.schild@siemens.com>,
"ibr@radix50.net" <ibr@radix50.net>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/8] CI rework of gitlab fast job
Date: Fri, 13 Jan 2023 04:34:59 +0000 [thread overview]
Message-ID: <190f85d82a42f66b4a95aa663097a9e5113c2e69.camel@siemens.com> (raw)
In-Reply-To: <20230113004315.65f968dc@md1za8fc.ad001.siemens.net>
On Fri, 2023-01-13 at 00:43 +0100, Henning Schild wrote:
> Am Thu, 12 Jan 2023 16:20:56 +0100
> schrieb Baurzhan Ismagulov <ibr@radix50.net>:
>
> > On Thu, Jan 12, 2023 at 04:12:50PM +0100, Henning Schild wrote:
> > > Yes the two should be orthogonal at the moment. I am just making
> > > fast a bit faster and go deeper ... because it now boots.
> >
> > As "fast" should remain the maintainer testsuite, I'd like to
> > discuss
> > the coverage implications with Anton as well.
>
> At the end of the day i want any variant of the testsuite to run on
> any
> setup just like it does on ilbers jenkins.
I fully agree. Currently it is really hard and time consuming to run
the testsuite, even just for basic tests.
>
> That should be based on the kas containers for anyone not using your
> jenkins.
This would also help a lot, to run it locally.
>
> With that any contributor would be able to run it manually or in
> their
> CI.
I guess this would also reduce the maintenance effort at Ilbers as less
patches would be sent to the ML which do not pass the CI.
Felix
>
> We currently can not run "full" in gitlab CI because it takes too
> much
> time and our gitlab runners would take such jobs for at most 12h. But
> that is a value i could adjust if we find that it really needs to
> take
> that long. I hope we can get much faster and still have the same
> coverage.
>
> Henning
>
> > > Since there have been no other review comments so far, i will
> > > prepare that v2 where all the "remove from fast" will have a
> > > generic reason and will be squashed.
> >
> > Yes, would be good.
> >
> >
> > With kind regards,
> > Baurzhan.
>
next prev parent reply other threads:[~2023-01-13 4:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 12:17 Henning Schild
2023-01-10 12:17 ` [PATCH 1/8] CI: move to avocado to 99.0 Henning Schild
2023-01-10 12:17 ` [PATCH 2/8] CI: fix shell coding style Henning Schild
2023-01-10 12:17 ` [PATCH 3/8] CI: install qemu-system when qemu testing is requested Henning Schild
2023-01-10 12:17 ` [PATCH 4/8] testsuite: remove Ccache test from "fast" set Henning Schild
2023-01-10 12:38 ` Jan Kiszka
2023-01-10 12:17 ` [PATCH 5/8] testsuite: remove Sdk " Henning Schild
2023-01-10 12:38 ` Jan Kiszka
2023-01-10 15:44 ` Henning Schild
2023-01-10 12:17 ` [PATCH 6/8] testsuite: remove ContainerImage " Henning Schild
2023-01-10 12:17 ` [PATCH 7/8] testsuite: remove ContainerSdk " Henning Schild
2023-01-10 12:17 ` [PATCH 8/8] testsuite: remove Sstate " Henning Schild
2023-01-10 12:24 ` [PATCH 0/8] CI rework of gitlab fast job Henning Schild
2023-01-12 12:23 ` Baurzhan Ismagulov
2023-01-12 15:12 ` Henning Schild
2023-01-12 15:20 ` Baurzhan Ismagulov
2023-01-12 23:43 ` Henning Schild
2023-01-13 4:34 ` Moessbauer, Felix [this message]
2023-01-13 13:14 ` Baurzhan Ismagulov
2023-01-13 17:14 ` Henning Schild
2023-01-14 14:40 ` Baurzhan Ismagulov
2023-01-23 8:26 ` Henning Schild
2023-04-02 19:13 ` Baurzhan Ismagulov
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=190f85d82a42f66b4a95aa663097a9e5113c2e69.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=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