[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220325115446.GP8939@worktop.programming.kicks-ass.net>
Date: Fri, 25 Mar 2022 12:54:46 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: "Chen, Rong A" <rong.a.chen@...el.com>
Cc: Nathan Chancellor <nathan@...nel.org>,
kernel test robot <lkp@...el.com>, x86-ml <x86@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [tip:sched/core] BUILD SUCCESS
3387ce4d8a5f2956fab827edf499fe6780e83faa
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.
Powered by blists - more mailing lists