All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Roger Pau Monne <roger.pau@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	ian.jackson@eu.citrix.com,
	"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>
Subject: Re: [xen-unstable test] 53884: regressions - FAIL
Date: Mon, 11 May 2015 09:12:29 +0100	[thread overview]
Message-ID: <5550646D.1010502@citrix.com> (raw)
In-Reply-To: <55507FB50200007800078C01@mail.emea.novell.com>

On 11/05/2015 09:08, Jan Beulich wrote:
>>>> On 09.05.15 at 20:57, <osstest@xenbits.xen.org> wrote:
>> flight 53884 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/53884/ 
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>>  build-amd64-xsm               5 xen-build                 fail REGR. vs. 50405
> This is due to e5786bae04 ("x86/pvh: use a custom IO bitmap for
> PVH hardware domains"). Having requested th addition during
> review I of course took it for granted that you build tested your
> change. As dealing with this imo also means moving the code
> addition into the already existing (or a new) CONFIG_X86 block
> (along with moving the declaration to a more suitable header), I
> think a fixup patch would not be the right way to deal with this,
> and hence I think I'm going to revert that change for the time
> being.

Given this reversion (and confirmation that the build is fixed), would a
force push be justified?  We are now a full month behind, with other 
OSSTest issues still outstanding.

~Andrew

  reply	other threads:[~2015-05-11  8:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09 18:57 [xen-unstable test] 53884: regressions - FAIL osstest service user
2015-05-11  8:08 ` Jan Beulich
2015-05-11  8:12   ` Andrew Cooper [this message]
2015-05-11  8:19     ` Jan Beulich
2015-05-11  8:29       ` Ian Campbell
2015-05-11  8:44         ` Jan Beulich
2015-05-11  8:32       ` Jan Beulich
2015-05-11  9:05         ` Ian Campbell
2015-05-11  9:38           ` Julien Grall
2015-05-11 10:50           ` Ian Campbell
2015-05-11  8:28     ` Ian Campbell
2015-05-11  8:48       ` Jan Beulich

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=5550646D.1010502@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.