From: Philip Li <philip.li@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
lkp@intel.com,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
oliver.sang@intel.com
Subject: Re: Notification of your branch being tested by zero day bot?
Date: Wed, 18 Sep 2019 15:39:19 +0800 [thread overview]
Message-ID: <20190918073919.GA1436@intel.com> (raw)
In-Reply-To: <20190918073138.GA1295@intel.com>
On Wed, Sep 18, 2019 at 03:31:38PM +0800, Philip Li wrote:
> On Fri, Sep 13, 2019 at 05:49:19AM +0100, Greg KH wrote:
> > (adding lkp@intel.com so that hopefully the right people see this)
> hi all, sorry for late notice, just back from china mid-autumn festival.
>
> >
> > On Thu, Sep 12, 2019 at 11:02:30AM -0400, Steven Rostedt wrote:
> > > Would it be possible to have an opt-in for the zero day bot to send an
> > > email when a branch is being tested? Similar to the "SUCCESS" opt-in
> > > email.
> do you mean something like BUILD start notification? This is good idea,
> we can support this.
>
> > >
> > > That is, it would be nice to see an email that lets you know that a
> > > branch you pushed to kernel.org is being tested. Currently there's a
> > > bit of limbo when a push happens, and you need to wait, perhaps several
> > > days, to see a result. In the mean time you have no idea if there's any
> > > progress going on. A notification would be nice.
> >
> > What is "implied" here is the fact that due to the flaky-ness of 0-day
> > these days, we really do not know if it is running or not.
> sorry that 0day ci had issue in July time frame, but it was recovered
> from August to generate report continuously. We will keep monitoring the
> healthy status to avoid any inconvenience.
Hi Greg, i checked stable-rc tree, it still had build incomplete notification
which means 0day ci had issue for this repo. Internally, we will not merge
stable tree to test in batch mode as others, which may be the cause of the
problem. We will look into this and figure out the solution.
Sorry again for the inconvenience.
>
> >
> > Lately it seems like it is "not" running, but due to the lack of any
> > status, it's really hard to tell how long a maintainer should wait
> > before "giving up" on getting a timely response and just relying on
> > their own judgement.
> Currently, if a repo is opt in for success notification, it will receive
> build incomplete if the full build test can't be done within 1 day.
> We will consider to enable this for all maintainer's repo.
>
> >
> > thanks,
> >
> > greg k-h
> >
next prev parent reply other threads:[~2019-09-18 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 15:02 Steven Rostedt
2019-09-13 4:49 ` Greg KH
2019-09-18 7:31 ` Philip Li
2019-09-18 7:39 ` Philip Li [this message]
2019-09-18 13:38 ` Steven Rostedt
2019-09-18 14:46 ` Philip Li
2019-09-18 19:47 ` Greg KH
2019-09-19 3:21 ` Philip Li
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=20190918073919.GA1436@intel.com \
--to=philip.li@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lkp@intel.com \
--cc=oliver.sang@intel.com \
--cc=rostedt@goodmis.org \
--cc=workflows@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox