From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [xen-4.0-testing test] 4854: regressions - FAIL
Date: Tue, 11 Jan 2011 05:19:39 +0000 [thread overview]
Message-ID: <osstest-4854-mainreport@xen.org> (raw)
flight 4854 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/4854/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-xcpkern-i386-pv 10 guest-saverestore fail REGR. vs. 4717
test-i386-i386-xl 9 guest-start fail REGR. vs. 4717
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-amd64-xl 15 guest-stop fail never pass
test-amd64-i386-rhel6hvm-amd 7 redhat-install fail never pass
test-amd64-i386-rhel6hvm-intel 7 redhat-install fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-amd64-i386-xl-credit2 9 guest-start fail blocked in 4717
test-amd64-i386-xl-multivcpu 15 guest-stop fail never pass
test-amd64-i386-xl 15 guest-stop fail never pass
test-amd64-xcpkern-i386-rhel6hvm-amd 7 redhat-install fail never pass
test-amd64-xcpkern-i386-rhel6hvm-intel 7 redhat-install fail never pass
test-amd64-xcpkern-i386-win 16 leak-check/check fail never pass
test-amd64-xcpkern-i386-xl-credit2 15 guest-stop fail never pass
test-amd64-xcpkern-i386-xl-multivcpu 15 guest-stop fail never pass
test-amd64-xcpkern-i386-xl 15 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-i386-xcpkern-i386-pv 18 leak-check/check fail REGR. vs. 4717
test-i386-xcpkern-i386-win 16 leak-check/check fail never pass
test-i386-xcpkern-i386-xl 15 guest-stop fail never pass
version targeted for testing:
xen 28646e7c54cc
baseline version:
xen ed6ff865366e
------------------------------------------------------------
People who touched revisions under test:
Keir Fraser <keir@xen.org>
------------------------------------------------------------
jobs:
build-i386-xcpkern pass
build-amd64 pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl fail
test-amd64-i386-xl fail
test-i386-i386-xl fail
test-amd64-xcpkern-i386-xl fail
test-i386-xcpkern-i386-xl fail
test-amd64-i386-rhel6hvm-amd fail
test-amd64-xcpkern-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 fail
test-amd64-xcpkern-i386-xl-credit2 fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-xcpkern-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu fail
test-amd64-xcpkern-i386-xl-multivcpu fail
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-xcpkern-i386-pair pass
test-i386-xcpkern-i386-pair pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv pass
test-amd64-xcpkern-i386-pv fail
test-i386-xcpkern-i386-pv fail
test-amd64-amd64-win fail
test-amd64-i386-win fail
test-i386-i386-win fail
test-amd64-xcpkern-i386-win fail
test-i386-xcpkern-i386-win fail
------------------------------------------------------------
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: 21430:28646e7c54cc
tag: tip
user: Keir Fraser <keir@xen.org>
date: Mon Jan 10 15:43:13 2011 +0000
Added signature for changeset 0bd829255a3f
changeset: 21429:caa0a152ca24
user: Keir Fraser <keir@xen.org>
date: Mon Jan 10 15:41:41 2011 +0000
Added tag 4.0.2-rc1 for changeset 0bd829255a3f
changeset: 21428:0bd829255a3f
tag: 4.0.2-rc1
user: Keir Fraser <keir@xen.org>
date: Mon Jan 10 15:41:30 2011 +0000
Update Xen version to 4.0.2-rc1
changeset: 21427:ed6ff865366e
user: Keir Fraser <keir@xen.org>
date: Sat Jan 08 10:45:22 2011 +0000
x86: Fix atomic_write*() macros to correctly inform GCC that memory
it knows about is being written to.
The bug is a copy-and-paste error from inline asm that writes to I/O
memory. In that case, as with asm for accessign guest memory,
specifying memory as a read-only parameter is acceptable because the
memory cannot alias with anything that GCC reads directly.
Signed-off-by: Keir Fraser <keir@xen.org>
xen-unstable changeset: 22683:533d6e5c0099
xen-unstable date: Sat Jan 08 10:05:55 2011 +0000
(qemu changes not included)
reply other threads:[~2011-01-11 5:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=osstest-4854-mainreport@xen.org \
--to=ian.jackson@eu.citrix.com \
--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 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.