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

Michael Ellerman
2024-10-24T03:59:20Z

Steven Rostedt <rostedt@goodmis.org> writes:
> On Wed, 23 Oct 2024 10:36:20 +0200
> Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
>> > To put it this way. The bugs I'm fixing was for code in linux-next
>> > where the bugs were never found. They only appeared when they went into
>> > Linus's tree. So why put the fixes in linux-next, if it didn't catch
>> > the bugs I fixed in the first place?
>>
>> Hmmm...
>>
>> Your arguments sound very similar to those being used in recent
>> discussions about not posting patches for public review...
>>
>> Please follow the process! ;-)
>
> What process?
>
...
>
> But pushing to linux-next for a day or two, what does that give me?

Several thousand build tests, across pretty much every architecture.

And a few hundred boot tests, lots virtualised, but some on real HW.

A single character typo in an #ifdef your testing doesn't cover can
break the build for lots of people ...

cheers