From: Nikolai Kondrashov <spbnick@gmail.com>
To: syzkaller <syzkaller@googlegroups.com>,
Dmitry Vyukov <dvyukov@google.com>,
Alice Ferrazzi <alicef@gentoo.org>,
automated-testing@lists.yoctoproject.org,
Cristian Marussi <cristian.marussi@arm.com>,
Johnson George <Johnson.George@microsoft.com>,
"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
Mark Brown <broonie@kernel.org>, Philip Li <philip.li@intel.com>,
Denys Fedoryshchenko <denys.f@collabora.com>,
Tales da Aparecida <tdaapare@redhat.com>,
Aditya Nagesh <adityanagesh@microsoft.com>,
Sachin Sant <sachinp@linux.ibm.com>,
Benjamin Copeland <Benjamin.Copeland@linaro.org>,
Manoj Kumar <ManojKumar08@arm.com>,
Michael Hofmann <mhofmann@redhat.com>,
marcelo.santos@profusion.mobi, kernelci-webdashboard@groups.io
Subject: Re: KCIDB: v5.2 - issue categories + 🗳 POLL
Date: Fri, 28 Mar 2025 11:11:00 +0200 [thread overview]
Message-ID: <aa001ed8-caa6-4e40-9eb0-940cbcab4e76@gmail.com> (raw)
In-Reply-To: <92698250-fab5-4f39-8f2d-3f29d85bdd40@gmail.com>
On 3/24/25 2:18 PM, Nikolai Kondrashov wrote:
> Hello, everyone involved with sending results to KCIDB,
>
> Please consider helping protocol development by filling this 5-minute form:
>
> 🗳️ https://forms.gle/FsZL84bcAzqve1aC8
>
> We now have full support for ingesting v5.1 schema, including the new
> "origin_builds_finish_time" and "origin_tests_finish_time" checkout fields.
>
> So, we could move onto the next change in v5.2, adding support for
> categorizing reported issues:
>
> https://github.com/kernelci/kcidb-io/pull/98/commits/e7ba6a9f351a724f69a556f7967f96bb83e398e4
This is now merged. Thank you everyone for attention!
If you think you can find the time, please consider participating in the poll:
🗳️ https://forms.gle/FsZL84bcAzqve1aC8
Nick
next prev parent reply other threads:[~2025-03-28 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 12:18 KCIDB: v5.2 - issue categories + 🗳 POLL Nikolai Kondrashov
2025-03-28 9:11 ` Nikolai Kondrashov [this message]
2025-03-31 11:58 ` 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=aa001ed8-caa6-4e40-9eb0-940cbcab4e76@gmail.com \
--to=spbnick@gmail.com \
--cc=Benjamin.Copeland@linaro.org \
--cc=Johnson.George@microsoft.com \
--cc=ManojKumar08@arm.com \
--cc=adityanagesh@microsoft.com \
--cc=alicef@gentoo.org \
--cc=automated-testing@lists.yoctoproject.org \
--cc=broonie@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=denys.f@collabora.com \
--cc=dvyukov@google.com \
--cc=kernelci-webdashboard@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=marcelo.santos@profusion.mobi \
--cc=mhofmann@redhat.com \
--cc=philip.li@intel.com \
--cc=sachinp@linux.ibm.com \
--cc=syzkaller@googlegroups.com \
--cc=tdaapare@redhat.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