From: Greg KH <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>, lkp@intel.com
Cc: "workflows@vger.kernel.org" <workflows@vger.kernel.org>
Subject: Re: Notification of your branch being tested by zero day bot?
Date: Fri, 13 Sep 2019 05:49:19 +0100 [thread overview]
Message-ID: <20190913044919.GB120223@kroah.com> (raw)
In-Reply-To: <20190912110230.483152ed@oasis.local.home>
(adding lkp@intel.com so that hopefully the right people see this)
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.
>
> 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.
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.
thanks,
greg k-h
next prev parent reply other threads:[~2019-09-13 4:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 15:02 Notification of your branch being tested by zero day bot? Steven Rostedt
2019-09-13 4:49 ` Greg KH [this message]
2019-09-18 7:31 ` Philip Li
2019-09-18 7:39 ` Philip Li
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=20190913044919.GB120223@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lkp@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;
as well as URLs for NNTP newsgroup(s).