mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Andi Kleen <andi@firstfloor.org>
Subject: Re: [GIT PULL] x86/asmlinkage changes for v3.12
Date: Fri, 04 Oct 2013 07:19:05 -0700	[thread overview]
Message-ID: <87685e2f-ea45-452b-8f6c-a2336d9cef67@email.android.com> (raw)
In-Reply-To: <20131004082847.GA30635@localhost>

Perfectly understandable.

Fengguang Wu <fengguang.wu@intel.com> wrote:
>On Wed, Sep 04, 2013 at 09:45:29AM -0700, H. Peter Anvin wrote:
>[snip]
>> This also exposes an interesting problem with Fengguang's build
>robot.
>> 
>> One build:
>> [tip:x86/asmlinkage] 28596b6a8779b736829ad837f95fdc2e81bdd1ee BUILD
>DONE
>> 28596b6a8779b736829ad837f95fdc2e81bdd1ee  x86, asmlinkage, vdso: Mark
>> vdso variables __visible
>> 
>> ... flags the warnings.  The next build for the branch looks clean:
>> [tip:x86/asmlinkage] eb86b5fd505cb97743d84226140cf247d91a2f03 BUILD
>SUCCESS
>> eb86b5fd505cb97743d84226140cf247d91a2f03  x86/asmlinkage: Fix warning
>in
>> xen asmlinkage change
>> 
>> ("DONE" means warnings or errors.)
>> 
>> A human observer would assume that the problem was fixed, since the
>> patch says "fix warnings", but the problem is that it didn't actually
>> fix *all* the warnings.  However, the bot has flagged the warnings as
>> preexisting from the previous build, and thus no new warnings were
>> introduced.
>
>Yeah sorry! The build robot silently ignored any reported errors,
>which is not the expected behavior when sending BUILD SUCCESS
>notifications.
>
>> It would be better if the bot reported any warnings not present in
>upstream.
>
>I've fixed the robot to remember which tree/branch first introduced
>the build error/warning. If the problem still remains in that branch's
>new HEAD, the robot will be able to send out BUILD DONE reports which
>will include the old error/warning message in the email body.
>
>Sorry for the delay! This feature was added shortly after your report,
>however took long time to confirm that it actually works.
>
>Thanks,
>Fengguang

-- 
Sent from my mobile phone.  Please pardon brevity and lack of formatting.

  reply	other threads:[~2013-10-04 14:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 14:39 Ingo Molnar
2013-09-04 15:58 ` Linus Torvalds
2013-09-04 16:45   ` H. Peter Anvin
2013-10-04  8:28     ` Fengguang Wu
2013-10-04 14:19       ` H. Peter Anvin [this message]
2013-10-04 14:20       ` H. Peter Anvin
2013-09-04 17:18   ` [tip:x86/asmlinkage] x86, paravirt: Remove duplicate definition for DEF_NATIVE tip-bot for H. Peter Anvin
2013-09-05  0:41   ` [GIT PULL] x86/asmlinkage changes for v3.12 Stephen Rothwell

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=87685e2f-ea45-452b-8f6c-a2336d9cef67@email.android.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=fengguang.wu@intel.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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

Powered by JetHome