From: Keir Fraser <keir.xen@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, xen-devel@lists.xensource.com
Cc: Olaf Hering <olaf@aepfle.de>
Subject: Re: [xen-4.0-testing test] 7147: regressions - FAIL
Date: Sat, 21 May 2011 23:19:54 +0100 [thread overview]
Message-ID: <C9FDF91A.1AC1F%keir.xen@gmail.com> (raw)
In-Reply-To: <osstest-7147-mainreport@xen.org>
Related to the -Wno-unused-but-set-variable patch. But this is weird because
the compiler runs many times with this option quite happily, before failing
on it as an unrecognised option much later in the build (building qemu in
this case, or stubdom in the case of xen-unstable). Any ideas?
-- Keir
On 21/05/2011 22:34, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
> flight 7147 xen-4.0-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/7147/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking:
> build-amd64-oldkern 4 xen-build fail REGR. vs.
> 7136
> build-amd64 4 xen-build fail REGR. vs.
> 7136
> build-i386-oldkern 4 xen-build fail REGR. vs.
> 7136
> build-i386 4 xen-build fail REGR. vs.
> 7136
>
> Tests which did not succeed, but are not blocking,
> including regressions (tests previously passed) regarded as allowable:
> test-amd64-amd64-pair 1 xen-build-check(1) blocked n/a
> test-amd64-amd64-pv 1 xen-build-check(1) blocked n/a
> test-amd64-amd64-win 1 xen-build-check(1) blocked n/a
> test-amd64-amd64-xl-win 1 xen-build-check(1) blocked n/a
> test-amd64-amd64-xl 1 xen-build-check(1) blocked n/a
> test-amd64-i386-pair 1 xen-build-check(1) blocked n/a
> test-amd64-i386-pv 1 xen-build-check(1) blocked n/a
> test-amd64-i386-rhel6hvm-amd 1 xen-build-check(1) blocked n/a
> test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a
> test-amd64-i386-win-vcpus1 1 xen-build-check(1) blocked n/a
> test-amd64-i386-win 1 xen-build-check(1) blocked n/a
> test-amd64-i386-xl-credit2 1 xen-build-check(1) blocked n/a
> test-amd64-i386-xl-multivcpu 1 xen-build-check(1) blocked n/a
> test-amd64-i386-xl-win-vcpus1 1 xen-build-check(1) blocked n/a
> test-amd64-i386-xl 1 xen-build-check(1) blocked n/a
> test-amd64-xcpkern-i386-pair 1 xen-build-check(1) blocked n/a
> test-amd64-xcpkern-i386-pv 1 xen-build-check(1) blocked n/a
> test-amd64-xcpkern-i386-rhel6hvm-amd 1 xen-build-check(1) blocked
> n/a
> test-amd64-xcpkern-i386-rhel6hvm-intel 1 xen-build-check(1) blocked
> n/a
> test-amd64-xcpkern-i386-win 1 xen-build-check(1) blocked n/a
> test-amd64-xcpkern-i386-xl-credit2 1 xen-build-check(1) blocked
> n/a
> test-amd64-xcpkern-i386-xl-multivcpu 1 xen-build-check(1) blocked
> n/a
> test-amd64-xcpkern-i386-xl-win 1 xen-build-check(1) blocked n/a
> test-amd64-xcpkern-i386-xl 1 xen-build-check(1) blocked n/a
> test-i386-i386-pair 1 xen-build-check(1) blocked n/a
> test-i386-i386-pv 1 xen-build-check(1) blocked n/a
> test-i386-i386-win 1 xen-build-check(1) blocked n/a
> test-i386-i386-xl-win 1 xen-build-check(1) blocked n/a
> test-i386-i386-xl 1 xen-build-check(1) blocked n/a
> test-i386-xcpkern-i386-pair 1 xen-build-check(1) blocked n/a
> test-i386-xcpkern-i386-pv 1 xen-build-check(1) blocked n/a
> test-i386-xcpkern-i386-win 1 xen-build-check(1) blocked n/a
> test-i386-xcpkern-i386-xl 1 xen-build-check(1) blocked n/a
>
> version targeted for testing:
> xen 9f8f91033546
> baseline version:
> xen c6034ee9b46e
>
> ------------------------------------------------------------
> People who touched revisions under test:
> Jan Beulich <jbeulich@novell.com>
> Keir Fraser <keir@xen.org>
> Olaf Hering <olaf@aepfle.de>
> ------------------------------------------------------------
>
> jobs:
> build-i386-xcpkern pass
> build-amd64 fail
> build-i386 fail
> build-amd64-oldkern fail
> build-i386-oldkern fail
> build-amd64-pvops pass
> build-i386-pvops pass
> test-amd64-amd64-xl blocked
> test-amd64-i386-xl blocked
> test-i386-i386-xl blocked
> test-amd64-xcpkern-i386-xl blocked
> test-i386-xcpkern-i386-xl blocked
> test-amd64-i386-rhel6hvm-amd blocked
> test-amd64-xcpkern-i386-rhel6hvm-amd blocked
> test-amd64-i386-xl-credit2 blocked
> test-amd64-xcpkern-i386-xl-credit2 blocked
> test-amd64-i386-rhel6hvm-intel blocked
> test-amd64-xcpkern-i386-rhel6hvm-intel blocked
> test-amd64-i386-xl-multivcpu blocked
> test-amd64-xcpkern-i386-xl-multivcpu blocked
> test-amd64-amd64-pair blocked
> test-amd64-i386-pair blocked
> test-i386-i386-pair blocked
> test-amd64-xcpkern-i386-pair blocked
> test-i386-xcpkern-i386-pair blocked
> test-amd64-amd64-pv blocked
> test-amd64-i386-pv blocked
> test-i386-i386-pv blocked
> test-amd64-xcpkern-i386-pv blocked
> test-i386-xcpkern-i386-pv blocked
> test-amd64-i386-win-vcpus1 blocked
> test-amd64-i386-xl-win-vcpus1 blocked
> test-amd64-amd64-win blocked
> test-amd64-i386-win blocked
> test-i386-i386-win blocked
> test-amd64-xcpkern-i386-win blocked
> test-i386-xcpkern-i386-win blocked
> test-amd64-amd64-xl-win blocked
> test-i386-i386-xl-win blocked
> test-amd64-xcpkern-i386-xl-win blocked
>
>
> ------------------------------------------------------------
> sg-report-flight on woking.cam.xci-test.com
> logs: /home/xc_osstest/logs
> images: /home/xc_osstest/images
>
> Logs, config files, etc. are available at
> http://www.chiark.greenend.org.uk/~xensrcts/logs
>
> Test harness code can be found at
> http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
>
>
> Not pushing.
>
> ------------------------------------------------------------
> changeset: 21495:9f8f91033546
> tag: tip
> user: Keir Fraser <keir@xen.org>
> date: Sat May 21 07:59:15 2011 +0100
>
> Added signature for changeset 82f6fd38f5c2
>
>
> changeset: 21494:50134c9b77ca
> user: Keir Fraser <keir@xen.org>
> date: Sat May 21 07:58:38 2011 +0100
>
> Added tag 4.0.2-rc4 for changeset 82f6fd38f5c2
>
>
> changeset: 21493:82f6fd38f5c2
> tag: 4.0.2-rc4
> user: Keir Fraser <keir@xen.org>
> date: Sat May 21 07:58:25 2011 +0100
>
> Update Xen version to 4.0.2-rc4
>
>
> changeset: 21492:19eefd764f6f
> user: Olaf Hering <olaf@aepfle.de>
> date: Sat May 21 07:57:03 2011 +0100
>
> gcc-4.6 compile fix: build with -Wno-unused-but-set-variable
>
> Avoid "error: variable 'unused' set but not used
> [-Werror=unused-but-set-variable]" with gcc 4.6.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
> xen-unstable changeset: 23368:0f670f5146c8
> xen-unstable date: Sat May 21 07:55:46 2011 +0100
>
>
> changeset: 21491:c6034ee9b46e
> user: Keir Fraser <keir@xen.org>
> date: Fri May 20 13:56:31 2011 +0100
>
> x86: clear CPUID output of leaf 0xd for Dom0 when xsave is disabled
>
> Linux starting with 2.6.36 uses the XSAVEOPT instruction and has
> certain code paths that look only at the feature bit reported through
> CPUID leaf 0xd sub-leaf 1 (i.e. without qualifying the check with one
> evaluating leaf 4 output). Consequently the hypervisor ought to mimic
> actual hardware in clearing leaf 0xd output when not supporting xsave.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
> xen-unstable changeset: 23353:a768a10d32b4
> xen-unstable date: Fri May 20 08:54:45 2011 +0100
>
> Make this unconditional for 4.0 (no pv xsave support) and fix for domU
> guests as well (this was already okay in 4.1 and later).
>
> Signed-off-by: Keir Fraser <keir@xen.org>
>
>
> (qemu changes not included)
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-21 22:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 21:34 [xen-4.0-testing test] 7147: regressions - FAIL xen.org
2011-05-21 22:19 ` Keir Fraser [this message]
2011-05-23 11:10 ` Olaf Hering
2011-05-23 12:32 ` Ian Campbell
2011-05-23 14:06 ` Ian Jackson
2011-05-23 15:08 ` Ian Jackson
2011-05-23 15:14 ` Ian Campbell
2011-05-23 15:18 ` Ian Jackson
2011-05-23 15:24 ` Keir Fraser
2011-05-23 15:33 ` Ian Jackson
2011-05-23 15:37 ` Keir Fraser
2011-05-23 15:40 ` Ian Jackson
2011-05-23 15:49 ` Keir Fraser
2011-05-23 16:16 ` Keir Fraser
2011-05-23 12:59 ` Olaf Hering
-- strict thread matches above, loose matches on Subject: below --
2011-05-22 16:29 M A Young
2011-05-22 18:10 ` [xen-4.0-testing " Keir Fraser
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=C9FDF91A.1AC1F%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).