From: "Nikolai Kondrashov" <Nikolai.Kondrashov@redhat.com>
To: kernelci@groups.io,
"automated-testing@yoctoproject.org"
<automated-testing@yoctoproject.org>
Subject: #KCIDB engagement report
Date: Mon, 24 May 2021 10:50:43 +0300 [thread overview]
Message-ID: <5a9bf050-0671-3273-cc4f-1b131445c1fe@redhat.com> (raw)
Hi everyone,
Below is the monthly report on KCIDB* engagement. It lists various CI systems
and their status of engagement with KCIDB, and once we get to that, will list
developer engagement.
Lines with updates are marked with "!".
Not much news this time, as I had to tend to CKI matters, and had a couple
weeks of vacation. I still have to tie some loose CKI ends before I return to
working on a new KCIDB release and reaching developers with e-mail
notifications.
However, I did try to contact Huawei's Compass CI with an invitation for
cooperation, but got no response so far.
KernelCI native
Sending (a lot of) production build and test results.
https://staging.kernelci.org:3000/?var-origin=kernelci
Red Hat CKI
Sending production results.
https://staging.kernelci.org:3000/?var-origin=redhat
Google Syzbot
Sending a subset of production results (failures only).
https://staging.kernelci.org:3000/?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. To be fixed soon.
https://staging.kernelci.org:3000/?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://staging.kernelci.org:3000/?var-origin=gkernelci
Intel 0day
Initial conversation concluded, general interest expressed,
no contact since.
Linaro
Sending (a lot of) Tuxsuite build results to "production" KCIDB.
https://staging.kernelci.org:3000/?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.
Please respond with corrections or suggestions of other CI systems to contact.
Nick
*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/
next reply other threads:[~2021-05-24 7:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 7:50 Nikolai Kondrashov [this message]
2021-05-24 17:38 ` #KCIDB engagement report 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
[not found] <8543af6d-28cf-6117-4dad-76aafea4b6f7@redhat.com>
2022-11-18 10:06 ` Guillaume Tucker
-- strict thread matches above, loose matches on Subject: below --
2022-07-23 11:50 Nikolai Kondrashov
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-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=5a9bf050-0671-3273-cc4f-1b131445c1fe@redhat.com \
--to=nikolai.kondrashov@redhat.com \
--cc=automated-testing@yoctoproject.org \
--cc=kernelci@groups.io \
/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.