Re: linus-next: improving functional testing for to-be-merged pull requests

[Sasha Levin <sashal@kernel.org>]

On Wed, Oct 30, 2024 at 10:08:57AM -0700, Paul E. McKenney wrote:
>On Mon, Oct 28, 2024 at 06:46:19PM -0400, Sasha Levin wrote:
>> On Mon, Oct 21, 2024 at 11:48:34PM -0700, Christoph Hellwig wrote:
>> > On Mon, Oct 21, 2024 at 09:54:53PM -0700, Kees Cook wrote:
>> > > For example, for a given PR, the bot can report:
>> > >
>> > > - Were the patches CCed to a mailing list?
>> > > - A histogram of how long the patches were in next (to show bake times)
>> > > - Are any patches associated with test failures? (0day and many other
>> > > CIs are already running tests against -next; parse those reports)
>> > >
>> > > We could have a real pre-submit checker! :)
>> >
>> > That would be very useful.  Items 1 and 2 should be trivial, 3 would
>> > require a bit of work but would still be very useful.
>>
>> If you've been following so far, there is a bot that is capable of doing
>> most of the above
>> (https://git.kernel.org/pub/scm/linux/kernel/git/sashal/next-analysis.git/).
>
>Nice!!!
>
>What does this make of these commits of mine?
>
>744e87210b1ae rcu: Finer-grained grace-period-end checks in rcu_dump_cpu_stacks()
>cbe644aa6fe17 rcu: Stop stall warning from dumping stacks if grace period ends
>26ff1fb02991e rcu: Delete unused rcu_gp_might_be_stalled() function

Days in linux-next:
----------------------------------------
  1 |
  2 |
  3 |
  4 |
  5 |
  6 | +++ (3)

-- 
Thanks,
Sasha