From: Nikolai Kondrashov <spbnick@gmail.com>
To: syzkaller <syzkaller@googlegroups.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vishal Bhoj <vishal.bhoj@linaro.org>,
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.1 - origin's build/test finish timestamps
Date: Wed, 19 Mar 2025 11:44:33 +0200 [thread overview]
Message-ID: <be02986c-0aed-4dc0-917f-c945aa20aed6@gmail.com> (raw)
In-Reply-To: <4697ff8f-7d97-4bcc-938f-958662289ba0@gmail.com>
On 3/14/25 8:21 PM, Nikolai Kondrashov wrote:
> We would like to add two fields to checkouts: "origin_builds_finish_time" and
> "origin_tests_finish_time". They're supposed to contain the time the CI system
> which sent the checkout has finished running the builds/tests it planned for it.
>
> As the change is minor and backwards-compatible, I'd like to set the feedback
> deadline to Wed, Mar 19. If there are no objections by that time, I'll merge
> this change to the schema and database support on that day.
This is now merged, thank you everyone for your attention.
Next I'll be testing and merging the DB support for this.
Nick
next prev parent reply other threads:[~2025-03-19 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 18:21 KCIDB: v5.1 - origin's build/test finish timestamps Nikolai Kondrashov
2025-03-19 9:44 ` Nikolai Kondrashov [this message]
2025-03-21 12:57 ` 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=be02986c-0aed-4dc0-917f-c945aa20aed6@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 \
--cc=vishal.bhoj@linaro.org \
/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