* b4 pr checks for KernelCI results
@ 2025-12-10 4:41 Mark Brown
2025-12-10 16:50 ` Arisu Tachibana
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Mark Brown @ 2025-12-10 4:41 UTC (permalink / raw)
To: Konstantin Ryabitsev; +Cc: tools, kernelci
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
Hi Konstantin,
It'd be really handy to have integration in b4 for querying the KernelCI
APIs for test results when both sending and pulling in PRs to see what
the testing state for the head commit for the PR is. There's some docs
for the API here:
https://docs.kernelci.org/
Possibly this could just be pointing at the dashboard if there's result
there, that'd be a start - there's a bunch of UI issues with starting to
get more complex.
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: b4 pr checks for KernelCI results
2025-12-10 4:41 b4 pr checks for KernelCI results Mark Brown
@ 2025-12-10 16:50 ` Arisu Tachibana
2026-03-06 21:09 ` Konstantin Ryabitsev
2026-03-06 21:15 ` B4 Bugbot
2 siblings, 0 replies; 4+ messages in thread
From: Arisu Tachibana @ 2025-12-10 16:50 UTC (permalink / raw)
To: Mark Brown; +Cc: Konstantin Ryabitsev, tools, kernelci
On Wed, Dec 10, 2025 at 1:41 PM Mark Brown <broonie@kernel.org> wrote:
>
> Hi Konstantin,
>
> It'd be really handy to have integration in b4 for querying the KernelCI
> APIs for test results when both sending and pulling in PRs to see what
> the testing state for the head commit for the PR is. There's some docs
> for the API here:
>
> https://docs.kernelci.org/
>
> Possibly this could just be pointing at the dashboard if there's result
> there, that'd be a start - there's a bunch of UI issues with starting to
> get more complex.
>
Hello everyone,
would be nice to have b4 integrated/using kci-dev (the official
KernelCI client tool)
the documentation is at https://kci.dev
https://github.com/kernelci/kci-dev
--
thanks,
arisut
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: b4 pr checks for KernelCI results
2025-12-10 4:41 b4 pr checks for KernelCI results Mark Brown
2025-12-10 16:50 ` Arisu Tachibana
@ 2026-03-06 21:09 ` Konstantin Ryabitsev
2026-03-06 21:15 ` B4 Bugbot
2 siblings, 0 replies; 4+ messages in thread
From: Konstantin Ryabitsev @ 2026-03-06 21:09 UTC (permalink / raw)
To: Mark Brown; +Cc: tools, kernelci
On Wed, Dec 10, 2025 at 01:41:47PM +0900, Mark Brown wrote:
> Hi Konstantin,
>
> It'd be really handy to have integration in b4 for querying the KernelCI
> APIs for test results when both sending and pulling in PRs to see what
> the testing state for the head commit for the PR is. There's some docs
> for the API here:
>
> https://docs.kernelci.org/
>
> Possibly this could just be pointing at the dashboard if there's result
> there, that'd be a start - there's a bunch of UI issues with starting to
> get more complex.
I'll look into this as part of the "check external CI systems" support in b4
review.
bugspray tag b4/review
--
KR
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: b4 pr checks for KernelCI results
2025-12-10 4:41 b4 pr checks for KernelCI results Mark Brown
2025-12-10 16:50 ` Arisu Tachibana
2026-03-06 21:09 ` Konstantin Ryabitsev
@ 2026-03-06 21:15 ` B4 Bugbot
2 siblings, 0 replies; 4+ messages in thread
From: B4 Bugbot @ 2026-03-06 21:15 UTC (permalink / raw)
To: broonie, kernelci, tools, konstantin
Hello:
This conversation is now tracked by b4 bug tracker.
There is no need to do anything else, just keep talking.
--
Deet-doot-dot, I am a bot.
b4 bug tracker (bugspray 0.1-dev)
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-03-06 21:15 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-12-10 4:41 b4 pr checks for KernelCI results Mark Brown
2025-12-10 16:50 ` Arisu Tachibana
2026-03-06 21:09 ` Konstantin Ryabitsev
2026-03-06 21:15 ` B4 Bugbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox