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: Thu, 24 Mar 2022 18:58:01 +0100 [thread overview]
Message-ID: <20220324175801.GJ8939@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <24dd031a-8ea7-5f01-4d80-3fb30d212c8a@intel.com>
On Tue, Mar 22, 2022 at 10:39:41AM +0800, Chen, Rong A wrote:
> On 3/22/2022 7:17 AM, Nathan Chancellor wrote:
> > Hello,
> >
> > On Tue, Mar 22, 2022 at 06:36:16AM +0800, kernel test robot wrote:
> > > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
> > > branch HEAD: 3387ce4d8a5f2956fab827edf499fe6780e83faa headers/prep: Fix header to build standalone: <linux/psi.h>
> > >
> > > elapsed time: 730m
> > >
> > > configs tested: 114
> > > configs skipped: 3
> > >
> > > The following configs have been built successfully.
> > > More configs may be tested in the coming days.
> > >
> > > gcc tested configs:
> > ...
> > > arm allyesconfig
> > > arm allmodconfig
> >
> > Are you sure these configurations built sucessfully?
...
> Thanks for your reminding, the problem commit is 4ff8f2ca6ccd
> ("sched/headers: Reorganize, clean up and optimize kernel/sched/sched.h
> dependencies"),
> the bot has sent two build reports related to it:
>
> https://lore.kernel.org/all/202203152116.qphmikIZ-lkp@intel.com/
> https://lore.kernel.org/all/202203152144.uFQqgVUf-lkp@intel.com/
>
> and more reports were stopped to avoid too many noise, like below one:
...
> We'll adjust the strategy avoid blocking some important reports.
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.
If you then falsly report the branch as being good, because you're
suppressing errors, things *will* go bad.
next prev parent reply other threads:[~2022-03-24 17:58 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 [this message]
2022-03-25 10:45 ` Chen, Rong A
2022-03-25 11:54 ` Peter Zijlstra
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=20220324175801.GJ8939@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