feedback about KernelCI reports

feedback about KernelCI reports

[Stephen Rothwell]

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

Hi,

Firstly, thanks for your testing and reporting.

Just a couple of simple thing:

It could be worth while reporting any tag on the HEAD commit.  This is
especially true for linux-next which comes out every day (with a tag)
- it would give people an upfront idea of which linux-next tree has a
problem.

Also, something is line wrapping your Log excerpt (and the reported
error/warning) which makes it harder to read.

-- 
Cheers,
Stephen Rothwell

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

Re: feedback about KernelCI reports

[Gustavo Padovan]

Hi Stephen,

Thanks a lot for your email. We appreciate the feedback!


---- On Fri, 04 Jul 2025 09:59:09 -0300 Stephen Rothwell <sfr@canb.auug.org.au> wrote ---

 > Hi, 
 >  
 > Firstly, thanks for your testing and reporting. 
 >  
 > Just a couple of simple thing: 
 >  
 > It could be worth while reporting any tag on the HEAD commit.  This is 
 > especially true for linux-next which comes out every day (with a tag) 
 > - it would give people an upfront idea of which linux-next tree has a 
 > problem. 


For sure. I can fix that quickly for you next week. Adding the tags
is definitelly possible. 

 > Also, something is line wrapping your Log excerpt (and the reported 
 > error/warning) which makes it harder to read. 

I am aware of that and tried a few things to solve this. It is something
in the Gmail API handling for the KernelCI bot. We'll look into it again.

Let us know of anything else you'd need. linux-next is a foundamental
piece of the Linux kernel integration process and the KernelCI organization
 would be happy to look at other needs you have. 

In the coming months, we should bring up regression reporting for
execution issues, eg boot failures, kseltests regressions, etc. Today
we only give you the builds, but kernel boots and tests the kernel
on a huge range of hardware configurations. We are working on strategies
to clean up data, otherwise, we just add noise to you with yet another
bot reporting things.

Best,

- Gus

Re: feedback about KernelCI reports

[Gustavo Padovan]

---- On Fri, 04 Jul 2025 14:17:59 -0300 Gustavo Padovan <gus@collabora.com> wrote ---

 > Hi Stephen, 
 >  
 > Thanks a lot for your email. We appreciate the feedback! 
 >  
 >  
 > ---- On Fri, 04 Jul 2025 09:59:09 -0300 Stephen Rothwell <sfr@canb.auug.org.au> wrote --- 
 >  
 >  > Hi, 
 >  > 
 >  > Firstly, thanks for your testing and reporting. 
 >  > 
 >  > Just a couple of simple thing: 
 >  > 
 >  > It could be worth while reporting any tag on the HEAD commit.  This is 
 >  > especially true for linux-next which comes out every day (with a tag) 
 >  > - it would give people an upfront idea of which linux-next tree has a 
 >  > problem. 
 >  
 >  
 > For sure. I can fix that quickly for you next week. Adding the tags 
 > is definitelly possible. 


I pushed a PR into the dashboard for adding tags. It should be in prod in a week or two.

https://github.com/kernelci/dashboard/pull/1337

 >  
 >  > Also, something is line wrapping your Log excerpt (and the reported 
 >  > error/warning) which makes it harder to read. 
 >  
 > I am aware of that and tried a few things to solve this. It is something 
 > in the Gmail API handling for the KernelCI bot. We'll look into it again. 

I also investigated this, but it seems to a deeper limitation into how Gmail API
handles plain text emails.  I tried a few things but nothing worked, even though
when I use that API fetch the e-mail that was just sent the content is not wrapped, 
but when a client shows it, there is a line wrap.

Maybe we need to a different approach or different mail server.

Best,

- Gus