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

[Sasha Levin]

On Mon, Nov 04, 2024 at 09:49:15AM +0100, Joel Granados 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/).
> >
> > Here's a histogram that describes v6.12-rc4..v6.12-rc5 as far as how
> > long commits spent in -next:
> >
> > Days in linux-next:
> > ----------------------------------------
> >   0 | +++++++++++++++++++++++++++++++++++++++++++++++++ (89)
> > <1 | +++++++++++ (21)
> >   1 | +++++++++++ (21)
> >   2 | +++++++++++++++++++++++++ (45)
> >   3 | ++++++++++++++ (25)
> >   4 | +++++ (10)
> >   5 |
> >   6 | + (2)
> >   7 |
> >   8 | + (3)
> >   9 | ++ (4)
> > 10 |
> > 11 | +++ (6)
> > 12 |
> > 13 |
> > 14+| ++++++++ (15)
> This looks super nice. Sometimes I need to answer how long a
> commit/series has been in next to either take it out of the PR or to at
> least have a comment to Linus.
> I see that I can use the script like `histo.sh /PATH/TO/DB COMMIT-ID`,
> which is exactly what I would expect.

Thanks!

> Is the idea to run the scripts from
> https://git.kernel.org/pub/scm/linux/kernel/git/sashal/next-analysis.git
> or to populate ones own DB in linux-next and then run histo?

You can use the DB in the git repo, but prep.sh is provided in case you
want to create your own or if I stop updating the repo for some reason.

--
Thanks,
Sasha