From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Doug Goldstein <cardoe@cardoe.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, osstest-admin@xenproject.org
Subject: Re: [xen-unstable test] 66454: regressions - FAIL
Date: Fri, 18 Dec 2015 14:24:26 +0000 [thread overview]
Message-ID: <1450448666.4053.230.camel@citrix.com> (raw)
In-Reply-To: <5674150A.2040904@citrix.com>
On Fri, 2015-12-18 at 14:15 +0000, Andrew Cooper wrote:
> On 18/12/15 13:33, Ian Campbell wrote:
> > > However, it is also wrong for OSSTest to be attempting to build a
> > > 32bit
> > > > hypervisor on any branch since 4.3. It seems to me that there is a
> > > > bug
> > > > there as well.
> > It is doing a build because it wants the 32 bit tools and it just does
> > a
> > make dist. This is perfectly fine behaviour IMHO.
> >
>
> Then "make dist" needs fixing. It is not fine to have the Xen component
> silently succeed and do nothing when asked to compile an invalid
> combination.
Feel free to change it, IMHO it's not that important.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-12-18 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 8:03 [xen-unstable test] 66454: regressions - FAIL osstest service owner
2015-12-18 11:02 ` Jan Beulich
2015-12-18 11:50 ` Ian Campbell
2015-12-18 12:52 ` Jan Beulich
2015-12-18 13:19 ` Andrew Cooper
2015-12-18 13:32 ` Jan Beulich
2015-12-18 13:33 ` Ian Campbell
2015-12-18 14:15 ` Andrew Cooper
2015-12-18 14:24 ` Ian Campbell [this message]
2015-12-18 14:24 ` Jan Beulich
2015-12-18 14:08 ` Doug Goldstein
2015-12-18 20:53 ` [PATCH] build: add support configuring for x86_32 Doug Goldstein
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=1450448666.4053.230.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=osstest-admin@xenproject.org \
--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.