All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Nikolai.Kondrashov@redhat.com,
	automated-testing@lists.yoctoproject.org,
	kernelci@lists.linux.dev
Subject: Re: #KCIDB engagement report
Date: Fri, 18 Nov 2022 11:06:17 +0100	[thread overview]
Message-ID: <4849d0f0-a3f4-bc8d-8af4-53e799c699be@collabora.com> (raw)
In-Reply-To: <8543af6d-28cf-6117-4dad-76aafea4b6f7@redhat.com>

+kernelci@lists.linux.dev (new KernelCI mailing list)

On 17/11/2022 11:28, Nikolai Kondrashov wrote:
> Hi everyone,
> 
> Below is the monthly* report on KCIDB** engagement. It lists various CI
> systems and their status of engagement with KCIDB, as well as developer
> engagement.
> 
> Lines with updates are marked with "!".
> 
> Main news are: Intel's 0day CI has been sending their data to production for a
> while, and are looking to expand their contribution, Microsoft moving closer
> to sending their data, and the proposal for known-issue schema is going out
> soon, after preliminary implementation and testing is complete.
> 
> CI Engagement Status
> 
>     KernelCI native
>         Sending (a lot of) production build and test results.
>         https://kcidb.kernelci.org/?var-origin=kernelci
> 
>     Red Hat CKI
>         Sending production results.
>         https://kcidb.kernelci.org/?var-origin=redhat
> 
>     Google Syzbot
>         Sending a subset of production results (failures only).
>         https://kcidb.kernelci.org/?var-origin=syzbot
> 
>     ARM
>         Sending production results.
>         Full commit hashes are currently not available, are spoofed, and don't
>         match the ones reported by others. There's ongoing switch to using a
>         KernelCI instance setup, which should fix this.
>         https://kcidb.kernelci.org/?var-origin=arm
> 
>     Sony Fuego
>         Internal design in progress.
> 
>     Gentoo GKernelCI
>         Sending production results.
>         Only builds (a few architectures), no configs, no logs, and no tests
>         for now, but working on growing contributions.
>         https://kcidb.kernelci.org/?var-origin=gkernelci
> 
>     Intel 0day
> !       Sending production results.
> !       Mainline builds and kselftest results.
> !       https://kcidb.kernelci.org/?var-origin=0dayci
> 
>     Linaro
>         Sending (a lot of) Tuxsuite build results to "production" KCIDB.
>         https://kcidb.kernelci.org/?var-origin=tuxsuite
> 
>     TuxML
>         Initial contact in response to a report.
>         There's a plan to approach us and start work in the coming months.
> 
>     Yocto Project
>         Initial contact in response to a report.
>         Would like to start sending build and test results, particularly for
>         older kernels. Would like to separate upstream commits from project
>         patches first: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14196
> 
>     Huawei Compass CI
>         Sent a message to Fengguang Wu, who was presenting it at LVC 2021.
>         No response so far.
> 
>     Microsoft
>         Johnson George was filled in on the details of submission process.
> 
> Please respond with corrections or suggestions of other CI systems to contact.
> 
> Thank you!
> Nick
> 
> *More-or-less :)
> 
> **KCIDB is an effort to unify Linux Kernel CI reporting, maintained by Linux
>   Foundation's KernelCI project:
>   https://foundation.kernelci.org/blog/2020/08/21/introducing-common-reporting/
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Groups.io Links: You receive all messages sent to this group.
> View/Reply Online (#1619): https://groups.io/g/kernelci/message/1619
> Mute This Topic: https://groups.io/mt/95087111/924702
> Mute #kcidb:https://groups.io/g/kernelci/mutehashtag/kcidb
> Group Owner: kernelci+owner@groups.io
> Unsubscribe: https://groups.io/g/kernelci/unsub [guillaume.tucker@collabora.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 
> 


       reply	other threads:[~2022-11-18 10:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8543af6d-28cf-6117-4dad-76aafea4b6f7@redhat.com>
2022-11-18 10:06 ` Guillaume Tucker [this message]
2022-07-23 11:50 #KCIDB engagement report Nikolai Kondrashov
  -- strict thread matches above, loose matches on Subject: below --
2022-06-20 12:48 Nikolai Kondrashov
2022-04-22 14:06 Nikolai Kondrashov
2022-01-27 14:41 Nikolai Kondrashov
2021-10-21 12:33 Nikolai Kondrashov
2021-08-23 12:37 Nikolai Kondrashov
2021-08-25 17:39 ` Nick Desaulniers
2021-06-16 13:54 Nikolai Kondrashov
2021-05-24  7:50 Nikolai Kondrashov
2021-05-24 17:38 ` Nick Desaulniers
2021-05-25 10:32   ` Nikolai Kondrashov
2021-06-01 19:10     ` Nick Desaulniers
2021-06-07 11:13       ` Nikolai Kondrashov
2021-06-07 18:09         ` Nick Desaulniers
2021-06-10  9:15           ` Nikolai Kondrashov
2021-06-10 23:38             ` Nick Desaulniers
2021-06-11 10:50               ` Nikolai Kondrashov
2021-06-11 11:10               ` Nikolai Kondrashov
2021-06-01 20:26   ` Kees Cook
2021-06-11 16:11     ` Guillaume Tucker
2021-06-15  9:58       ` Nikolai Kondrashov
2021-06-15 10:36         ` Guillaume Tucker
2021-06-15 22:03       ` Kees Cook
2021-06-15 22:23         ` Guillaume Tucker
2021-06-15 23:02           ` Kees Cook
2021-06-30  8:54             ` Guillaume Tucker
2021-06-30 18:19               ` Kees Cook
2021-04-15  8:54 Nikolai Kondrashov
2021-03-18 10:34 Nikolai Kondrashov
2021-02-18 10:47 Nikolai Kondrashov

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=4849d0f0-a3f4-bc8d-8af4-53e799c699be@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=Nikolai.Kondrashov@redhat.com \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=kernelci@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.