Re: [Ksummit-discuss] [CORE TOPIC] Issues with stable process

[Fengguang Wu <fengguang.wu@intel.com>]

On Thu, Jul 16, 2015 at 12:19:04PM +0300, James Bottomley wrote:
> On Wed, 2015-07-15 at 21:25 -0400, Steven Rostedt wrote:
> > On Thu, 16 Jul 2015 09:24:10 +1000
> > NeilBrown <neilb@suse.com> wrote:
> > 
> > > > I just use the rule of thumb: must be in -next for two days because then
> > > > I know 0day (and the other checkers) have also run.
> > > 
> > > Do you *really* know that?
> > > Given that there seems to be value in knowing "0day has run
> > > successfully", should we ask for an interface to do exactly that?
> > > 
> > 
> > There's an opt-in with Fengguang Wu's 0day tests to have it email you
> > when it finishes with "SUCCESS". I have that, as I don't do pushes for
> > any patches until I see that.
> 
> How?  Is there actually some sort of interface to 0day? (/me has been
> rather lazy and simply emails requests to Fengguang).  Detail would be
> great to share.

Just send me an email and say something like

        I'd like to get build completion notification for git URLs

            git://neil.brown.name/md
            git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git

Then I'll add them to the notification list.

The build completion notification will be private emails to the
committer of each branch's HEAD commit. It will typically be sent
out 1-2 hours after your git push.

But note the email only means the "quick" set of about 100 kconfigs
are finished and the build farm is in healthy state.

To improve coverage, we added 2 features in the past year to let
0day system run kind of endless more tests in machine idle time:

- hundreds more randconfig + all defconfigs in arch/*/configs/**
- commit by commit testing
 
So if you want to be reasonably safe, consider waiting for 1 day
before sending out your patch.

Thanks,
Fengguang