All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Gustavo Padovan <gus@collabora.com>
Cc: kernelci <kernelci@lists.linux.dev>,
	linux-rt-devel <linux-rt-devel@lists.linux.dev>,
	stable-rt <stable-rt@vger.kernel.org>,
	Daniel Wagner <wagi@monom.org>
Subject: Re: PREEMPT_RT testing on kernelci
Date: Thu, 17 Apr 2025 17:11:13 +0200	[thread overview]
Message-ID: <20250417151113.W9MG8dy3@linutronix.de> (raw)
In-Reply-To: <19643df8092.ac2e879d858176.2114269254543526159@collabora.com>

On 2025-04-17 10:10:43 [-0300], Gustavo Padovan wrote:
> 
> 
> ---- On Thu, 17 Apr 2025 07:04:10 -0300 Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote ---
> 
>  > On 2025-04-14 12:14:44 [-0300], Gustavo Padovan wrote: 
>  > > Hi Sebastian, 
>  > Hi Gustavo, 
>  >  
>  > > In my understanding you want to know when results for any rt-tests change status (eg PASS -> FAIL or 
>  > > vice versa) for a selection of trees (eg mainline, next, etc). Can you confirm? 
>  >  
>  > The results change is definitely interesting. The other thing is what is 
>  > tested and how. I remember you added/ changed some architectures for the 
>  > RT subset. I also assume that warnings at bootime (as in lockdep or 
>  > general warnings) are reported. 
> 
> We have some support around that, but this work is still evolving.

Okay.

>  > I remember Daniel asked for some cyclictests/rt-tests integration so I 
>  > don't know what is tested here ;) 
>  >  
>  > From the commandline you sent that there are a few boards running the 
>  > cyclictests and everything either passes or is in state "INCONCLUSIVE". 
>  > So this looks nice. 
> 
> Okay.
> 
> As for notifications, for which trees/branches you want to see it?

Linus' master and the -next tree would be good. If you plan add to add
Cc here, it would be nice if you could add linux-rt-devel@lists.linux.dev

Sebastian

  reply	other threads:[~2025-04-17 15:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11  9:05 PREEMPT_RT testing on kernelci Sebastian Andrzej Siewior
2025-02-11 11:33 ` Gustavo Padovan
2025-02-11 15:20   ` Sebastian Andrzej Siewior
2025-02-11 15:50     ` Gustavo Padovan
2025-02-11 16:26       ` Mark Brown
2025-02-13  8:52       ` Sebastian Andrzej Siewior
2025-04-11 19:44         ` Sebastian Andrzej Siewior
2025-04-14 15:14           ` Gustavo Padovan
2025-04-17 10:04             ` Sebastian Andrzej Siewior
2025-04-17 13:10               ` Gustavo Padovan
2025-04-17 15:11                 ` Sebastian Andrzej Siewior [this message]
2025-04-18 15:05                   ` Gustavo Padovan
2025-02-11 15:33 ` Guenter Roeck
2025-02-11 15:37   ` Sebastian Andrzej Siewior
2025-02-11 15:49     ` Guenter Roeck
2025-02-12 17:17   ` Donald Zickus
2025-02-12 17:59     ` Guenter Roeck

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=20250417151113.W9MG8dy3@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=gus@collabora.com \
    --cc=kernelci@lists.linux.dev \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=stable-rt@vger.kernel.org \
    --cc=wagi@monom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.