All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: Jan Beulich <JBeulich@suse.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 08:08:55 -0600	[thread overview]
Message-ID: <56741377.9060807@cardoe.com> (raw)
In-Reply-To: <5673F5EF02000078000C11C9@prv-mh.provo.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1915 bytes --]

On 12/18/15 5:02 AM, Jan Beulich wrote:
>>>> On 18.12.15 at 09:03, <osstest-admin@xenproject.org> wrote:
>> flight 66454 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/66454/ 
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>>  build-i386                    5 xen-build                 fail REGR. vs. 66415
>>  build-i386-xsm                5 xen-build                 fail REGR. vs. 66415
> 
> Doug,
> 
> this needs fixing:
> 
> ***
> *** Can't find default configuration "arch/x86/configs/x86_32_defconfig"!
> ***
> make[2]: Leaving directory `/home/osstest/build.66454.build-i386-xsm/xen/xen'
> make[1]: Leaving directory `/home/osstest/build.66454.build-i386-xsm/xen/xen'
> gcc  -O1 -fno-omit-frame-pointer -m32 -march=i686 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O0 -g3 -D__XEN_TOOLS__ -MMD -MF .xc_core.o.d -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls -mno-tls-direct-seg-refs -D_GNU_SOURCE  -I../../xen/common/libelf -Werror -Wmissing-prototypes -I. -I./include -I/home/osstest/build.66454.build-i386-xsm/xen/tools/libxc/../../tools/include -pthread -include /home/osstest/build.66454.build-i386-xsm/xen/tools/libxc/../../tools/config.h  -c -o xc_core.o xc_core.c 
> make[2]: *** [defconfig] Error 1
> make[1]: *** [.config] Error 2
> make: *** [install-xen] Error 2
> 
> Previously build attempts on ix86 resulted in no error, with just
> 
> *** Xen x86/32 target no longer supported!
> 
> printed.
> 
> Jan
> 

Sure not a problem. I actually had this support in there but one of the
early review comments was to drop x86_32 support (you'll notice I
mention it in the changelog for v2).

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2015-12-18 14:09 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
2015-12-18 14:24         ` Jan Beulich
2015-12-18 14:08   ` Doug Goldstein [this message]
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=56741377.9060807@cardoe.com \
    --to=cardoe@cardoe.com \
    --cc=JBeulich@suse.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.