From: Peter Zijlstra <peterz@infradead.org>
To: "Chen, Rong A" <rong.a.chen@intel.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
kernel test robot <lkp@intel.com>, x86-ml <x86@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [tip:sched/core] BUILD SUCCESS 3387ce4d8a5f2956fab827edf499fe6780e83faa
Date: Fri, 25 Mar 2022 12:54:46 +0100 [thread overview]
Message-ID: <20220325115446.GP8939@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <2d37183b-e0d5-dd37-11c7-9b0e415daaf4@intel.com>
On Fri, Mar 25, 2022 at 06:45:24PM +0800, Chen, Rong A wrote:
> > Oh *PLEASE* never report a branch as building if there's errors.
> > It could be I (force) push a branch multiple times before I get any
> > 0day reports back (0day has gotten *soooo* slow) so I only ever look at
> > the latest report -- possibly days later.
>
> Hi Peter,
>
> Sorry for the bad experience, I'm not sure the meaning of "a branch as
> building", is there a way to know the branch is not ready, or we can
> postpone the test for a branch by a day?
I was just commenting in general; never send a mail with "SUCCESS" in
the subject (as per this thread) when there are errors/warns with it,
supressed or otherwise.
If you do want to supress warnings (I'm not sure why; a few more emails
in my inbox really aren't going to make a difference) then please state
so explicitly with a link to the email with the report.
The thing I worry about is that I often wait for a SUCCESS mail from
0day robot before I push code to tip. If the SUCCESS is unreliable, this
is not good.
next prev parent reply other threads:[~2022-03-25 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 22:36 [tip:sched/core] BUILD SUCCESS 3387ce4d8a5f2956fab827edf499fe6780e83faa kernel test robot
2022-03-21 23:17 ` Nathan Chancellor
2022-03-22 2:39 ` Chen, Rong A
2022-03-24 17:58 ` Peter Zijlstra
2022-03-25 10:45 ` Chen, Rong A
2022-03-25 11:54 ` Peter Zijlstra [this message]
2022-03-25 13:07 ` Chen, Rong A
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=20220325115446.GP8939@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=rong.a.chen@intel.com \
--cc=x86@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