From: Peter Zijlstra <peterz@infradead.org>
To: Rong Chen <rong.a.chen@intel.com>
Cc: Marco Elver <elver@google.com>, kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [kbuild-all] Re: [PATCH] compiler_attributes.h: Support no_sanitize_undefined check with GCC 4
Date: Wed, 17 Jun 2020 10:30:41 +0200 [thread overview]
Message-ID: <20200617083041.GD2531@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200617010051.GS5653@shao2-debian>
On Wed, Jun 17, 2020 at 09:00:51AM +0800, Rong Chen wrote:
> On Tue, Jun 16, 2020 at 03:19:21PM +0200, Peter Zijlstra wrote:
> > 301805 N + Jun 16 kernel test rob (5.8K) [peterz-queue:x86/entry] BUILD SUCCESS 8e8bb06d199a5aa7a534aa3b3fc0abbbc11ca438
> >
> > Why that thing is claiming SUCCESS when it introduces a build error I
> > don't know.
> Sorry for the misunderstanding, some folks complained that it's too
> noisy when there're only new warnings in a "BUILD REGRESSION" report,
> so we changed to use "BUILD SUCCESS" if there's no new build error. To
> avoid misunderstanding, we'll change build complete report title to
> "BUILD SUCCESS WITH WARNING" for new warnings.
Thanks Rong!
next prev parent reply other threads:[~2020-06-17 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202006160328.6MfJNuqX%lkp@intel.com>
2020-06-15 23:15 ` [PATCH] compiler_attributes.h: Support no_sanitize_undefined check with GCC 4 Marco Elver
2020-06-16 13:09 ` Miguel Ojeda
2020-06-16 13:19 ` Peter Zijlstra
2020-06-17 1:00 ` [kbuild-all] " Rong Chen
2020-06-17 8:30 ` Peter Zijlstra [this message]
2020-06-17 8:30 ` [tip: x86/entry] " tip-bot2 for Marco Elver
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=20200617083041.GD2531@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=elver@google.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rong.a.chen@intel.com \
--cc=tglx@linutronix.de \
/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