b4 pr checks for KernelCI results

b4 pr checks for KernelCI results

[Mark Brown]

[-- 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 --]

Re: b4 pr checks for KernelCI results

[Arisu Tachibana]

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

Re: b4 pr checks for KernelCI results

[Konstantin Ryabitsev]

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

Re: b4 pr checks for KernelCI results

[B4 Bugbot]

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)

b4 review looses thread on update

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

Hi Konstantin,

I had a review of v1 of:

   e53aefc63e28caf32bcd553f3d0a8f2a5a25cd8d.1773193726.git.xiaopei01@kylinos.cn

which showed that v2 was available.  When I did actions->update (mildly
annoying that that's a captial U BTW) b4 flashed up a screen saying that
it couldn't work out a base and then returned me to the list, with the
series gone from the list.  I'd have expected to get to pick a base in
that case (ideally it'd remember what branch it was previously targeted
at).

Thanks,
Mark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: b4 review looses thread on update

[Konstantin Ryabitsev]

On Wed, Mar 11, 2026 at 12:14:09PM +0000, Mark Brown wrote:
> Hi Konstantin,
> 
> I had a review of v1 of:
> 
>    e53aefc63e28caf32bcd553f3d0a8f2a5a25cd8d.1773193726.git.xiaopei01@kylinos.cn
> 
> which showed that v2 was available.  When I did actions->update (mildly
> annoying that that's a captial U BTW) b4 flashed up a screen saying that
> it couldn't work out a base and then returned me to the list, with the
> series gone from the list.  I'd have expected to get to pick a base in
> that case (ideally it'd remember what branch it was previously targeted
> at).

Yes, this code is very lightly tested and has seen a lot of churn. Let me
see what's happening there. Thanks!

bugspray tag b4/review

-- 
KR