[Automated-testing] CKI project introduction

[Veronika Kabatova]

----- Original Message -----
> From: "Tim Bird" <Tim.Bird at sony.com>
> To: vkabatov at redhat.com, automated-testing at yoctoproject.org
> Sent: Tuesday, March 26, 2019 9:00:12 PM
> Subject: RE: CKI project introduction
> 
> Veronika and other CKI people,
> 
> Hi and welcome to this list!
> 
> Here's a brief intro to this list and some links to our resources.
> https://elinux.org/Automated_Testing
> 

Thanks for the link! I'll check it out (together with the other resources you
mention below) as I have time.

> Do you have a public web site for CKI?  If so, can you provide that,
> or add the link yourself to this page (under Test Automation Tools):
> https://elinux.org/Test_Systems
> 

Yes, we are at cki-project.org (although there's not much info yet). I'll
request an account and add the link.

> The inception of this community came about based on some board farm
> and automated testing talks and sessions at ELC Europe 2017.  Some of the
> information
> from that event was preserved here:
> https://elinux.org/Board_Farm
> 
> I'll describe below what we've been working on, and what I think would be
> good next steps to coordinate our work.
> 
> > -----Original Message-----
> > From: automated-testing-bounces at yoctoproject.org
> > 
> > Hi,
> > 
> > I've been told it will be useful to introduce our project on this list :)
> > We
> > are a team of people from Red Hat dealing with automated testing for
> > kernel,
> > both for internal kernels and for upstream.
> > 
> > We are mostly focused on testing on different architectures (x86_64, ppc64,
> > ppc64le, s390x) for Fedora, RHEL and stable kernels but would like to
> > expand
> > to other upstream sources later. We do some testing for mainline but aren't
> > sending those reports anywhere yet.
> > 
> > If you'd like to know more details about how we do things please check out
> > the
> > talk from this year's DevConf [0]. Some of our code can be found on GitHub
> > [1]
> > and GitLab [2]. Eventually we'd like to make even more parts of our
> > pipeline
> > public, as we sanitize out internal data etc.
> 
> That sounds great.  I just had time to check out the first few minutes of the
> talk,
> but will plan to check out the rest of the talk, and your source code, soon.
> 
> > 
> > I'd also like to link our reports for stable kernels [3] and stable queue
> > [4]
> > so you can see which tests we run for upstream without having to dig
> > through
> > our repos.
> > 
> > While we don't have a public IRC channel yet, we can be reached at
> > <cki-project at redhat.com>. Some of us also already joined this list and were
> > invited over to #linaro-lkft so we can discuss possible collaboration with
> > other upstream kernel CI systems.
> 
> Thanks.  I would definitely like to compare notes, and see what we can
> learn from and leverage from your system.
> 

I'm planning to write up a few posts explaining technical details and stuff like
that later (and they'll be also linked from the project website) if that would
help. We are also still evolving our pipelines so things will likely change in
the future.

> > 
> > We are also planning a sort-of-hackfest/meeting with upstream and CI
> > people
> > during Plumbers this year [5]. We heard there was an Automated Testing
> > Summit
> > last year collocated with OSS. If it happened during Plumbers this year we
> > would be excited to join, however I'm not sure if we'd be able to
> > participate
> > otherwise.
> > 
> > Please reach out on any of the channels if you have any questions for us,
> > Veronika
> > 
> > [0] https://www.youtube.com/watch?v=9KwDWsAqivo
> > [1] https://github.com/cki-project/
> > [2] https://gitlab.com/cki-project/
> > [3] https://lists.linaro.org/pipermail/linux-stable-mirror/2019-
> > March/096629.html
> > [4] https://lists.linaro.org/pipermail/linux-stable-mirror/2019-
> > March/096639.html
> > [5] https://linuxplumbersconf.org/event/4/
> 
> OK. Thanks.
> 
> At the Automated Testing Summit in 2018, we tried to come to agreement on
> a few things: terminology, an overall CI reference description (based on a
> diagram
> by me and Kevin Hilman), and a set of next steps for working together on
> Linux
> CI standards.
> See https://elinux.org/Automated_Testing_Summit
> (slides and videos from the event are linked from that page)
> Also, see https://elinux.org/Test_Glossary and
> https://elinux.org/Test_Standards
> 
> We would like to learn more about your system, to see how it fits with our
> conception of
> the CI loop that we use in embedded Linux testing.   To help use share
> information
> among ourselves, we created a survey, which I can send to you if you are
> willing
> to fill it out.  You can see the survey and responses for other Linux test
> systems at:
> https://elinux.org/Test_Stack_Survey
> 

Absolutely! Should I make a page with our answers on the web or do you have a
different way of recording them?

We don't do any embedded system testing since that's not what our customers
care about (although I personally love embedded) but hopefully we can still
collaborate on making the kernel better.

> Finally, now is probably a good time to talk about the status of our efforts,
> and when
> we plan to get together again.
> 
> I'll start that discussion in another thread on this list.
> 
> It is nice to hear from you, and learn about your testing initiatives and
> software.

Thanks!

Veronika

>  -- Tim
> 
> 
>