From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [xen-unstable test] 8316: tolerable FAIL - PUSHED
Date: Fri, 5 Aug 2011 05:52:40 +0100 [thread overview]
Message-ID: <osstest-8316-mainreport@xen.org> (raw)
flight 8316 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/8316/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-i386-i386-pv 5 xen-boot fail pass in 8312
test-amd64-i386-xl-multivcpu 5 xen-boot fail pass in 8308
test-amd64-i386-pair 8 xen-boot/dst_host fail pass in 8312
test-amd64-i386-pair 7 xen-boot/src_host fail pass in 8312
test-amd64-i386-xl-win-vcpus1 5 xen-boot fail pass in 8308
test-amd64-i386-win-vcpus1 5 xen-boot fail in 8312 pass in 8316
test-amd64-i386-pv 5 xen-boot fail in 8308 pass in 8316
test-i386-i386-win 5 xen-boot fail in 8308 pass in 8316
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail never pass
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-amd64-i386-rhel6hvm-amd 5 xen-boot fail like 8289
test-amd64-i386-xl 5 xen-boot fail like 8289
test-amd64-amd64-xl 5 xen-boot fail like 8289
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-i386-i386-xl-win 13 guest-stop fail never pass
test-amd64-amd64-pair 8 xen-boot/dst_host fail like 8289
test-amd64-amd64-pair 7 xen-boot/src_host fail like 8289
test-i386-i386-xl 5 xen-boot fail in 8312 like 8289
test-i386-i386-pair 7 xen-boot/src_host fail in 8312 like 8289
test-i386-i386-pair 8 xen-boot/dst_host fail in 8312 like 8289
test-amd64-amd64-xl-win 5 xen-boot fail in 8308 like 8289
test-i386-i386-xl-win 5 xen-boot fail in 8308 like 8289
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail in 8308 never pass
version targeted for testing:
xen 0f36c2eec2e1
baseline version:
xen fa4e2ca9ecff
------------------------------------------------------------
People who touched revisions under test:
Anthony PERARD <anthony.perard@citrix.com>
Christoph Egger <Christoph.Egger@amd.com>
George Dunlap <george.dunlap@eu.citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
Keir Fraser <keir@xen.org>
Olaf Hering <olaf@aepfle.de>
Tim Deegan <Tim.Deegan@citrix.com>
------------------------------------------------------------
jobs:
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 pass
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 pass
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu fail
test-amd64-amd64-pair fail
test-amd64-i386-pair fail
test-i386-i386-pair pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv fail
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-xl-win-vcpus1 fail
test-amd64-amd64-win fail
test-amd64-i386-win fail
test-i386-i386-win fail
test-amd64-amd64-xl-win fail
test-i386-i386-xl-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
Pushing revision :
+ branch=xen-unstable
+ revision=0f36c2eec2e1
+ . cri-lock-repos
++ . cri-common
+++ umask 002
+++ getconfig Repos
+++ perl -e '
use Osstest;
readconfigonly();
print $c{Repos} or die $!;
'
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ '[' x '!=' x/export/home/osstest/repos/lock ']'
++ OSSTEST_REPOS_LOCK_LOCKED=/export/home/osstest/repos/lock
++ exec with-lock-ex -w /export/home/osstest/repos/lock ./ap-push xen-unstable 0f36c2eec2e1
+ branch=xen-unstable
+ revision=0f36c2eec2e1
+ . cri-lock-repos
++ . cri-common
+++ umask 002
+++ getconfig Repos
+++ perl -e '
use Osstest;
readconfigonly();
print $c{Repos} or die $!;
'
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ '[' x/export/home/osstest/repos/lock '!=' x/export/home/osstest/repos/lock ']'
+ : xen@xenbits.xensource.com
+ : xen@xenbits.xensource.com:git/linux-pvops
+ : master
+ : tested/2.6.39.x
+ case "$branch" in
+ cd /export/home/osstest/repos/xen-unstable.hg
+ hg push -r 0f36c2eec2e1 ssh://xen@xenbits.xensource.com/HG/xen-unstable.hg
pushing to ssh://xen@xenbits.xensource.com/HG/xen-unstable.hg
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 2 changesets with 7 changes to 7 files
reply other threads:[~2011-08-05 4:52 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-8316-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.