Content-Type: multipart/mixed; boundary="===============2047546196976564181==" MIME-Version: 1.0 From: Peter Zijlstra To: kbuild-all@lists.01.org Subject: Re: [PATCH] compiler_attributes.h: Support no_sanitize_undefined check with GCC 4 Date: Wed, 17 Jun 2020 10:30:41 +0200 Message-ID: <20200617083041.GD2531@hirez.programming.kicks-ass.net> In-Reply-To: <20200617010051.GS5653@shao2-debian> List-Id: --===============2047546196976564181== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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! --===============2047546196976564181==--